GNOME Bugzilla – Bug 411504
segfaults if dbus session bus not available
Last modified: 2007-07-11 10:26:14 UTC
Steps to reproduce: 1. Suspend and resume overnight. 2. Notice that you are unable to launch programs from the panel (pressing an icon results in the appropriate loading animation and seemingly a process being spawned but no program appears) 3. In a terminal type killall gnome-settings-daemon 4. In the same terminal type gnome-settings-daemon Stack trace: Memory status: size: 28610560 vsize: 0 resident: 28610560 share: 0 rss: 7340032 rss_rlim: 0 CPU usage: start_time: 1172305386 rtime: 0 utime: 20 stime: 0 cutime:16 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-settings-daemon' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226570064 (LWP 17246)] [New Thread -1228219488 (LWP 17248)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 113450
Thread 1 (Thread -1226570064 (LWP 17246))
Other information: For a good 5-10 minutes this bug was reproducible every time an attempt was made to launch gnome-settings-daemon. After this period things that had previously not restarted themselves like the panel suddenly relaunched themselves (as did gnome-settings-daemon). The following was seen on the console: ~$ gnome-settings-daemon (gnome-settings-daemon:16999): GSwitchIt-WARNING **: Unable to connect to dbus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'm an dbus-daemon' for help) ** (gnome-settings-daemon:16999): CRITICAL **: dbus_g_connection_register_g_obje ct: assertion `connection != NULL' failed ** (gnome-settings-daemon:16999): CRITICAL **: dbus_g_proxy_new_for_name: assert ion `connection != NULL' failed ** (gnome-settings-daemon:16999): CRITICAL **: dbus_g_proxy_call: assertion `DBU S_IS_G_PROXY (proxy)' failed ** (bug-buddy:17005): WARNING **: Couldn't load icon for Open Folder Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x1a00003 (Bug Buddy); these messages lack timestamps and therefore suck. Bug Buddy did not recognize the gnome-control-center program and didn't automatically upload this bug to bugzilla. Version Information: Ubuntu Edgy gnome-control-center 2.16.1-0ubuntu4.2
That looks very much like a problem in libxklavier/libgnomekbd. Sergey, can you please take a look?
Confirming. Easily reproducable by not starting a session bus before running g-s-d. The keyboard libs can't handle that.
I have this on my system - but actually the keyboard stuff survives missing dbus. It seems g-s-d crashes later, when it is trying to connect its own dbus service (used by the gnome-session).
Created attachment 85054 [details] [review] fix crash if dbus not available Ok, so this one fixes the crash, but I still get a number of critical warnings, at least some of which are from the keyboard stuff: (gnome-settings-daemon:4909): GnomeKbdIndicator-WARNING **: Unable to connect to dbus: Failed to connect to socket /tmp/dbus-KBxn0HzBsW: Connection refused ** (gnome-settings-daemon:4909): CRITICAL **: dbus_g_connection_register_g_object: assertion `connection != NULL' failed ** (gnome-settings-daemon:4909): CRITICAL **: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed (gnome-settings-daemon:4909): GnomeKbdIndicator-CRITICAL **: Could not create DBUS proxy ** (gnome-settings-daemon:4909): WARNING **: Unable to connect to dbus: Failed to connect to socket /tmp/dbus-KBxn0HzBsW: Connection refused
Remaining critical warnings are in libgnomekbd. Reassigning.
I made config registry stop initialization if klass->connection is NULL. Fixed in SVN. Could you please check whether it works for you lads?