With gnome-settings-daemon 3.0.2-1ubuntu3 (and possibly earlier versions, I haven't tried), this bug appears to be reliably producible by launching a second concurrent instance of gnome-settings-daemon (i.e., running it when it's already running). I have gotten this to happen on two separate, similarly configured Oneiric i386 systems in unity-2d sessions by running "gnome-settings-daemon" in Terminal windows. While gnome-settings-daemon needn't support multiple instances, a second instance of gnome-settings-daemon should gracefully exit--it should not segfault (and in any case, there may well be other situations where this crash occurs).
On one of the Oneiric i386 systems, I was able to produce a better stack trace. I have reported that crash as duplicate bug 796497. Are others able to reliably reproduce this crash the same way? If so, we can edit the bug's description to include it as an easy way to make the crash happen. ek@Nyaa:~$ gnome-settings-daemon ** (gnome-settings-daemon:1932): WARNING **: You can only run one xsettings manager at a time; exiting ** (gnome-settings-daemon:1932): WARNING **: Unable to start xsettings manager: Could not initialize xsettings manager. ** (gnome-settings-daemon:1932): WARNING **: Name taken or bus went away - shutting down Segmentation fault (core dumped) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788710 Title: gnome-settings-daemon crashed with SIGSEGV in exit() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/788710/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
