gnome-settings-daemon crashed with SIGSEGV in gnome_settings_plugin_activate()

Bug #188572 reported by Adam Blackburn
562
This bug affects 118 people
Affects Status Importance Assigned to Milestone
gnome-control-center
Fix Released
Critical
gnome-settings-daemon (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-settings-daemon

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)

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Feb 3 18:18:36 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
NonfreeKernelModules: floppy
Package: gnome-settings-daemon 2.21.90.1-0ubuntu3
PackageArchitecture: i386
ProcCmdline: gnome-settings-daemon
ProcCwd: /home/adam
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_HK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 gnome_settings_plugin_activate ()
Title: gnome-settings-daemon crashed with SIGSEGV in gnome_settings_plugin_activate()
Uname: Linux mountain 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

Tags: apport-crash
Revision history for this message
Adam Blackburn (adamblackburn) wrote :
Revision history for this message
Adam Blackburn (adamblackburn) wrote :

Output from gnome-settings-daemon

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:impl_activate (plugin=0x812eb30) at gsd-screensaver-plugin.c:80
gnome_settings_plugins_engine_activate_plugin (info=0x8130220)
gnome_settings_plugins_engine_load_dir (
gnome_settings_plugins_engine_load_dir (
gnome_settings_plugins_engine_init (

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in gnome-settings-daemon:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=514385

Changed in gnome-settings-daemon:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in gnome-control-center:
status: Unknown → Fix Released
Revision history for this message
Per Osbeck (perosb) wrote :

I seem to be suffering from the same bug.

It seems to be fixed by upstream now though:
http://svn.gnome.org/viewvc/gnome-settings-daemon?view=revision&revision=100

Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :

Same here on two upgrade hardy pc...

Thank you

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Fixed upstream.

Changed in gnome-settings-daemon:
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-settings-daemon - 2.21.91-0ubuntu1

---------------
gnome-settings-daemon (2.21.91-0ubuntu1) hardy; urgency=low

  * New upstream version:
    - Use a flat directory instead of a hierarchy to install plugins into
    - Don't scan the plugins directory recursively
    - Install the settings plugin to a versioned directory to fix install
      with libdir == libexecdir
    - Review short and long descriptions for GConf keys
    - Don't crash when running the screensaver fails (lp: #188572)
    - Rename src folder to gnome-settings-daemon
    - Add uninstalled.pc file for building against an uninstalled copy of g-s-d
    - Add separate checks for libbackground and use external copy
    - Use gnome_settings_daemon for the GConf path
    - Release the Glade XML ASAP and keep track of the 2 widgets we need
    - Make sure we return a GError if initialization fails
    - Load the XKB settings initially
    - Fix leaks
    - Unref the GConfClient only after done with it
    - Check for xinput
    - Fix copy'n'paste error
    - Declare variables at the beginning of a block
      to make older compilers happy
    - Add back support for defining plugin start order
    - Assign return value from g_slist_sort to the plugins list variable
    - Replace gnome_vfs usage with GIO
  * debian/control.in:
    - updated libglib requirement
  * debian/gnome-settings-daemon.install:
    - new version changes
  * debian/patches/80_from_upstream_fix_xkb_loading.patch,
    debian/patches/90_configure_xinput_change.patch:
    - dropped, fixed in the new version

 -- Sebastien Bacher <email address hidden> Mon, 11 Feb 2008 17:54:34 +0100

Changed in gnome-settings-daemon:
status: Fix Committed → Fix Released
Revision history for this message
bergfreak (laotse-sein) wrote :

I seem to be suffering from the same bug...

Revision history for this message
crtm (carlosrtm) wrote :

just starts the booting sequence of the interface when logging on me as a normal user, failure occurs

Changed in gnome-control-center:
importance: Unknown → Critical
Revision history for this message
ckx (john2-hendrickx) wrote :

I got this error message on a fresh install of Ubuntu 11.10 beta-1. All updates had been installed and I'd rebooted, then I updated the language packs. I got this error message after that had completed.

Revision history for this message
Morgan van Dyk (morgan-van-dyk) wrote :

I installed Ubuntu 11.10 Beta and then after update this appeared. Hope it help someone but scary that its one week before release and things like this still happening

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.