GNOME Bugzilla – Bug 690898
gnome-settings-daemon seagfaults when started
Last modified: 2013-04-10 16:36:10 UTC
Created attachment 232405 [details] gnome-settings-daemon --debug output Gnome-settings-daemon 3.4.2+git20120925.a4c817-2 from debian testing. Running gnome-settings-daemon --debug produces the output found in attached gsd-debug.log Running gdb gnome-settings-daemon produces the output found in attached gsd-gdb.log
Created attachment 232406 [details] output of gdb gnome-settings-daemon
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! (And running a gnome-settings-daemon in debug mode when one is already running isn't very useful, see the: ** (gnome-settings-daemon:20560): WARNING **: You can only run one xsettings manager at a time; exiting line)
> Please see http://live.gnome.org/GettingTraces for more information I have closely followed the procedure described in http://live.gnome.org/GettingTraces (more specifically instructions for Debian found via https://live.gnome.org/GettingTraces/DistroSpecificInstructions) before providing these crash logs. > And running a gnome-settings-daemon in debug mode when one is already running isn't very useful, see the: I'm not running a gnome-session and don't have another gnome-settings-daemon running. (that was the point, I need it be running to make use of GNOME's power management ). See: $ sudo update-alternatives --display x-session-manager x-session-manager - auto mode link currently points to /usr/bin/lxsession /usr/bin/lxsession - priority 49 slave x-session-manager.1.gz: /usr/share/man/man1/lxsession.1.gz /usr/bin/openbox-session - priority 40 slave x-session-manager.1.gz: /usr/share/man/man1/openbox-session.1.gz Current 'best' version is '/usr/bin/lxsession'. $ ps aux | grep settings-daemon baron 4149 0.0 0.3 54068 3652 ? Sl 14:59 0:00 /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper baron 23622 0.0 0.0 3568 780 pts/1 S+ 19:23 0:00 grep settings-daemon
andre on IRC told me I should run thread apply all bt in gdb after the crash occurs to obtain a full stack trace. Maybe this info should be added to https://live.gnome.org/GettingTraces as I wouldn't have found it without his help. Thanks andre. Attaching gnome-settings-daemon stacktrace, hope it will help.
Created attachment 233523 [details] g-s-d stacktrace
The mouse plugin lacks debug information, so the backtrace isn't very helpful. I think it's crashing while trying to handle the idle and we're exiting, but I can't certain as the plugin lacks debug information. Please install the debug packages for your distribution. This patch might fix it: commit 9d6e80924ff9011dc2d8caa8a49a588ff4a318bd Author: Bastien Nocera <hadess@hadess.net> Date: Tue Jan 15 14:55:38 2013 +0100 mouse: Stop idle start when stop() is called Might fix: https://bugzilla.gnome.org/show_bug.cgi?id=690898 (In reply to comment #3) > I'm not running a gnome-session and don't have another gnome-settings-daemon > running. (that was the point, I need it be running to make use of GNOME's power > management ). That's not really something we support, and I would expect all kinds of things being broken if you did that.
I have disabled the mouse plugin and this doesn't happen anymore. Better close this bug.
If you're not willing to help debug the problem, or it's fixed by the patch above, certainly.