After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 658278 - gnome-settings-daemon crashed with SIGSEGV
gnome-settings-daemon crashed with SIGSEGV
Status: RESOLVED INCOMPLETE
Product: gnome-settings-daemon
Classification: Core
Component: media-keys
3.1.x
Other Linux
: High critical
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-05 17:13 UTC by Pedro Villavicencio
Modified: 2011-09-05 17:35 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2


Description Pedro Villavicencio 2011-09-05 17:13:44 UTC 
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/839867

g-s-d is crashing on startup with:

.

+ Trace 228337

Thread 1 (Thread 0xb77a7840 (LWP 1099))

  • #0 on_bus_gotten
    at gsd-media-keys-manager.c line 2219
  • #1 check_socket
    at /build/buildd/glib2.0-2.29.18/./gio/gsocket.c line 271
  • #2 ??
    from /tmp/tmpRMsg5G/usr/lib/i386-linux-gnu/libdbus-glib-1.so.2 
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Comment 1 Bastien Nocera 2011-09-05 17:35:07 UTC 
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!