gnome-screensaver crashed with SIGSEGV in g_datalist_id_set_data_full()

[Addamaccada]

happens within a few seconds of unity starting up

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-screensaver 3.0.0-2ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Tue Jul 26 10:11:16 2011
ExecutablePath: /usr/bin/gnome-screensaver
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x4fcd34 <g_datalist_id_set_data_full+356>: mov 0x0(%ebp),%ecx
 PC (0x004fcd34) ok
 source "0x0(%ebp)" (0xaaaaaaa8) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-screensaver
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-screensaver crashed with SIGSEGV in g_datalist_id_set_data_full()
UpgradeStatus: Upgraded to oneiric on 2011-07-26 (0 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 g_data_set_internal (datalist=0x9f43d68, key_id=53, data=0x0, destroy_func=0) at /build/buildd/glib2.0-2.29.14/./glib/gdataset.c:372
 g_datalist_id_set_data_full (datalist=0x9f43d68, key_id=53, data=0x0, destroy_func=0) at /build/buildd/glib2.0-2.29.14/./glib/gdataset.c:673
 g_object_real_dispose (object=0x9f43d60) at /build/buildd/glib2.0-2.29.14/./gobject/gobject.c:895
 gtk_widget_dispose (object=0x9f43d60) at /build/buildd/gtk+3.0-3.1.10/./gtk/gtkwidget.c:10622
 g_object_unref (_object=0x9f43d60) at /build/buildd/glib2.0-2.29.14/./gobject/gobject.c:2709

[Pedro Villavicencio (pedro)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=655434