Red Hat Bugzilla – Bug 480392
banshee 1.4.1 sometimes crashes
Last modified: 2011-04-06 07:49:38 EDT
Created attachment 329247 [details]
Description of problem:
I installed fedora 10 in 64 bits, I was looking for some good music media player rythmhbox has a very low volume and doesn't has equalizer, amarok 2 doesn't work in gnome and when you can do it to work it has also very low volume then I found banshee and it worked OK. After some fedora 10 updates it began to crash.
When you run it sometimes the window appears but you can do nothing, the window becomes gray and when you try to close it, fedora kill the process. If you try to re-open with good-luck it works.
When I run strace it has some problems with gcc and mono libs as you can see in the attachment
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I've seen very similar behaviour. Tried it just now with --debug and saw these warnings:
** (Banshee:4589): WARNING **: Symbol file /usr/lib64/mono/gac/Mono.Zeroconf/188.8.131.52__e60c4f4a95e1099e/Mono.Zeroconf.dll.mdb has incorrect version (expected 50.0, got 39)
** (Banshee:4589): WARNING **: Symbol file /usr/lib64/mono-zeroconf/Mono.Zeroconf.Providers.Avahi.dll.mdb has incorrect version (expected 50.0, got 39)
** (Banshee:4589): WARNING **: Symbol file /usr/lib64/mono-zeroconf/Mono.Zeroconf.Providers.Bonjour.dll.mdb has incorrect version (expected 50.0, got 39)
in case that's relevant.
The Zeroconf error is harmless, as far as I can tell -- see
It appears to be harmless, but if that's bothersome, you can contact the mono-zeroconf and ndesk-dbus-glib maintainers. The packages have not been rebuilt since F-9 because there are no new release since then.
As to the intermittent crashes, are they fixed if you remove Banshee configuration files? rm -rf $HOME/.gconf/apps/banshee-1 and killall gconfd-2, and try starting Banshee again. It should not affect your music library, just the preferences.
Just tried that and the crash after startup still happened.
Oddly, if I do start from a terminal with --debug, it starts normally. Perhaps it's a timing issue, and the slowdown from the debug output works around it?
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.