GNOME Bugzilla – Bug 356479
gnome-setting-daemon crashes just after X starts
Last modified: 2007-10-02 17:44:56 UTC
Distribution: Gentoo Base System version 1.12.4 Package: GConf Severity: Normal Version: GNOME2.15.92 unspecified Gnome-Distributor: Gentoo Synopsis: gnome-setting-daemon crashes just after X starts Bugzilla-Product: GConf Bugzilla-Component: gconf Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.15.91) Description: Description of the crash: There wasn't a choice for gnome-settings-daemon; gconf seemed the closest match. My ~/.xinitrc starts gconfd-2 and gnome-settings-daemon before starting urxvtd and then icewm. g-s-d gets a SEGV and bug buddy is running by the time icewm is ready. I run X from a vc login with startx. Steps to reproduce the crash: 1. startx 2. 3. How often does this happen? Always. Additional Information: gentoo box, bleeding egde gnome and gtk ebuilds. Debugging Information: Backtrace was generated from '/usr/libexec/gnome-settings-daemon' Using host libthread_db library "/usr/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227991376 (LWP 30498)] [New Thread -1228035168 (LWP 30506)] 0xb7ef8410 in ?? ()
+ Trace 72615
------- Bug created by bug-buddy at 2006-09-18 03:11 -------
Created attachment 76210 [details] gnome-setting-daemon crashes just after X starts Fedora 6 with last ATI driver ( ati-driver-installer-8.30.3) on Compag nx9420 laptop. 01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600]
Moving to right product
There are dbus-related error messages in the trace, so could you try removing gconfd from your .xinitrc file (it's automatically started when needed by client apps) and replace it with: /usr/bin/dbus-launch --exit-with-session /usr/bin/gnome-session Does that change anything? Of course, we should not crash if dbus is not available though.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 370025 ***