GNOME Bugzilla – Bug 347344
Segmentation fault at DBus.Bus:GetSessionBus()
Last modified: 2006-09-04 23:41:18 UTC
Segmentation fault occurs at DBus.Bus:GetSessionBus() in PowerManagement::FindInstance(). Banshee can't be launched. I'm using dbus 0.61.
How about a trace? http://banshee-project.org/Debugging This is not a blocker.
Back trace isn't helpful. But the problem is in DBus.Bus:GetSessionBus(). ******************************** [kazhik@red:145]~% gdb mono GNU gdb Red Hat Linux (6.3.0.0-1.122rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run /usr/local/lib/banshee/banshee.exe Starting program: /usr/bin/mono /usr/local/lib/banshee/banshee.exe Reading symbols from shared object read from target memory...(no debugging symbols found)...done. Loaded system supplied DSO at 0xc1a000 (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208633648 (LWP 3035)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread -1219708000 (LWP 3058)] [New Thread -1219724384 (LWP 3059)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Initializing Component Connecting to GConf... (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Initializing Component Detecting network settings... Warning: [2006/07/15 7:55:01] (Cannot connect to NetworkManager) - An available, working network connection will be assumed Initializing Component Creating action manager... Initializing Component Loading music library... [New Thread -1227199584 (LWP 3061)] (no debugging symbols found) (no debugging symbols found) Initializing Component Initializing GStreamer... Initializing Component Initializing player engine... Debug: [2006/07/15 7:55:04] (Default player engine) - GStreamer 0.10 Initializing Component Initializing Audio CD support... Debug: [2006/07/15 7:55:04] (Audio CD Core Initialized) - Setting MusicBrainz proxy to www.musicbrainz.org:80 [New Thread -1230021728 (LWP 3062)] Initializing Component Initializing Digital Audio Player support... [New Thread -1247433824 (LWP 3063)] Initializing Component Initializing CD Burning support... ** (/usr/local/lib/banshee/banshee.exe:3035): WARNING **: nautilus_burn_drive_copy is deprecated please use nautilus_burn_drive_ref() instead Initializing Component Initializing plugins... [New Thread -1248281696 (LWP 3064)] Audioscrobbler starting protocol engine Initializing Component Initializing power management... Program received signal SIGSEGV, Segmentation fault.
+ Trace 69340
Thread NaN (LWP 3035)
IP 0xef04c3 at offset 0x53 of method DBus.Bus:GetBus (DBus.Bus/BusType) (0xef0470 0xef0518)[domain 0x21f00 - banshee.exe] $1 = 0
Confirmed on Fedora Core 5:- Backtrace (well not really but the whole thing): (gdb) run Starting program: /usr/bin/mono --debug /usr/lib/banshee/banshee.exe Reading symbols from shared object read from target memory...(no debugging symbols found)...done. Loaded system supplied DSO at 0x4c0ac000 (no debugging symbols found) <snip> (no debugging symbols found) (no debugging symbols found) Warning: [8/9/2006 12:42:07 AM] (Cannot connect to NetworkManager) - An available, working network connection will be assumed [New Thread -1229771872 (LWP 30191)] (no debugging symbols found) Debug: [8/9/2006 12:42:11 AM] (Default player engine) - GStreamer 0.10 Debug: [8/9/2006 12:42:11 AM] (Audio CD Core Initialized) - [New Thread -1231287392 (LWP 30192)] ** (/usr/lib/banshee/banshee.exe:30185): WARNING **: nautilus_burn_drive_copy is deprecated please use nautilus_burn_drive_ref() instead Program received signal SIGSEGV, Segmentation fault.
+ Trace 70109
Thread NaN (LWP 30185)
Fedora Core 5 using:- DBus 0.61 Mono 1.1.13.7
The same crash was reported as bug 350482.
*** Bug 350482 has been marked as a duplicate of this bug. ***
I created a new Linux user account, changed to it by "su - <newuser>" in gnome-terminal, and launched banshee. Segmentation fault didn't occur. I returned the account from <newuser> by "su - kazhik", and launched banshee. Segmentation fault didn't occur too. ******************************************** [kazhik@red:63]~% banshee Warning: [08/25/2006 07:18:19] (Cannot connect to NetworkManager) - An available, working network connection will be assumed Debug: [08/25/2006 07:18:20] (Default player engine) - GStreamer 0.10 Debug: [08/25/2006 07:18:20] (Audio CD Core Initialized) - ** (/usr/local/lib/banshee/banshee.exe:2876): WARNING **: nautilus_burn_drive_copy is deprecated please use nautilus_burn_drive_ref() instead Setting MusicBrainz proxy to www.musicbrainz.org:80 Warning: [08/25/2006 07:18:20] (Power Management Call Failed) - Cannot find GNOME Power Manager: Unable to determine the address of the message bus Warning: [08/25/2006 07:18:20] (Could not connect to D-Bus) - D-Bus support will be disabled for this instance: Unable to determine the address of the message bus (Banshee:2876): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference. ******************************************** Is dbus configuration wrong?
This is probably a distro-specific DBus/dbus-sharp problem. Additionally, it may also be a Mono problem. The GPM code in Banshee is not apparently at fault. In FindInstance, if there's a problem connecting to DBus or finding GPM on the session bus, an exception should be thrown by dbus-sharp, which will be properly handled in Banshee. However, it appears that Mono is just aborting when there's a DBus problem, which doesn't allow the proper Banshee error handling to even kick in.