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

Bug #182293 reported by fragro
This bug report is a duplicate of:  Bug #122438: Compiz Crash. Edit Remove
14
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-control-center

ProblemType: Crash
Architecture: i386
Date: Sat Jan 12 14:29:15 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gnome-control-center/gnome-settings-daemon
NonfreeKernelModules: cdrom
Package: gnome-control-center 1:2.21.4-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-settings-daemon
ProcCwd: /home/fragro
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_datalist_id_set_data_full ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: gnome-settings-daemon crashed with SIGSEGV in g_datalist_id_set_data_full()
Uname: Linux fragro-laptop 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 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
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_datalist_id_set_data_full (datalist=0x81fb840, key_id=49, data=0x0, destroy_func=0)
g_object_real_dispose (object=0x81fb838)
gtk_object_dispose (gobject=0x81fb838)
gtk_widget_dispose (object=0x81fb838)
gtk_window_dispose (object=0x81fb838)

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in gnome-control-center:
importance: Undecided → Medium
Revision history for this message
rah003 (rah-atlas) wrote :

Hi,
I just got the exactly same crash on hardy. I see this is marked as a duplicate of the compiz issue against 7.10 which is in turn marked as invalid.
Since it is still happening I don't think the status is right.

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

Other bug subscribers

Remote bug watches

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