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 514385 - gnome-settings-daemon crashed with SIGSEGV in gnome_settings_plugin_activate()
gnome-settings-daemon crashed with SIGSEGV in gnome_settings_plugin_activate()
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: plugins
2.21.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2008-02-04 19:07 UTC by Pedro Villavicencio
Modified: 2008-02-04 21:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Pedro Villavicencio 2008-02-04 19:07:39 UTC 
this bug has been entered here:

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

"started laptop, on login the box appeared stating that gnome-settings-daemon had failed to start. Running gnome-settings-daemon with the terminal (output from the terminal is attached)"

".

+ Trace 188084

Thread 1 (process 5585)

  • #0 impl_activate
    at gsd-screensaver-plugin.c line 80
  • #1 gnome_settings_plugins_engine_activate_plugin
    at gnome-settings-plugins-engine.c line 516
  • #2 gnome_settings_plugins_engine_load_dir
    at gnome-settings-plugins-engine.c line 260
  • #3 gnome_settings_plugins_engine_load_dir
    at gnome-settings-plugins-engine.c line 293
  • #4 gnome_settings_plugins_engine_init
    at gnome-settings-plugins-engine.c line 308
  • #5 gnome_settings_manager_start
    at gnome-settings-manager.c line 106
  • #6 main
    at main.c line 221 






Comment 1


Jens Granseuer





          2008-02-04 21:07:00 UTC
        



Unfortunately, it seems like compiler optimiations have greatly reduced the usefulness of the stacktrace (e.g. it doesn't show very precisely where it happened), but I suspect it's fixed with this commit:

2008-02-04  Jens Granseuer  <jensgr@gmx.net>

        * plugins/screensaver/gsd-screensaver-manager.c:
        (gsd_screensaver_manager_start): don't crash when running the
        screensaver fails. The plugin relies on the GError it passes always
        being filled in if we couldn't start the module, so set it up properly
        in those cases (bug #514385)