GNOME Bugzilla – Bug 625395
Banshee crashes on startup: Extension `Banshee.MultimediaKeys.MultimediaKeysService' not started: No support GNOME Settings Daemon could be reached.
Last modified: 2010-09-22 14:27:39 UTC
Created attachment 166644 [details] The output from "banshee-1 --debug --debug-sql" I'm running Kubuntu Linux 9.10, and I've installed Banshee 1.7.3 from the official Karmic PPA repository. Every time I try to start banshee, the main window appears for a a second, and then the program crashes. I've tried deleting Banshee's preferences directory and starting it again, and it still crashes. I'm not sure what's going on, but I've attached a log file that contains the output from running "banshee-1 --debug --debug-sql".
That log does not show the crash exception. Please run Banshee again, without --debug-sql this time, eg: `banshee-1 --debug > banshee-log.txt` and then attach the banshee-log.txt file.
Created attachment 167674 [details] Output from "banshee-1 --debug > banshee-log.txt"
Created attachment 170505 [details] The output from "banshee-1 --debug > banshee-log.txt" For reference, I just upgraded to banshee 1.7.5 and it still crashes. Here's the output log.
There still is no crash in that log, are you sure it crashes and doesn't just hang?
Maybe you have to redirect the error output too? Using: banshee-1 --debug > log.txt 2>&1
Created attachment 170836 [details] Output from "banshee-1 --debug > log.txt 2>&1" For what it's worth, it seems like a crash to me; the main Banshee window appears for about half a second and then disappears, and the exit status code in the console is "1". It doesn't seem to generate a core file, though...
By any chance if you disable the notification area extension does this go away? Could possibly be: https://bugzilla.gnome.org/show_bug.cgi?id=626935 Also I got a report via irc yesterday that the same BadMatch error was happening in KDE but not in GNOME from slomo I believe.
That appears to have fixed the problem. Thanks!
Thanks *** This bug has been marked as a duplicate of bug 626935 ***