[ dbgsym ] gnome-settings-daemon crashed with SIGSEGV in g_object_unref()

Bug #840819 reported by dino99
6
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

crash at each boot on Oneiric i386 b1

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.90-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic-pae 3.0.4
Uname: Linux 3.0.0-10-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Sep 4 09:49:53 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb7205f1b: mov (%eax),%edx
 PC (0xb7205f1b) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 conf_watcher_finalize (object=0xb5b14120) at conf-watcher.c:32
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in g_object_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
dino99 (9d9) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #840326, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-i386-retrace
Revision history for this message
dino99 (9d9) wrote :

valgrind output:

oem@oem-desktop:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrindGSD.log /usr/lib/gnome-settings-daemon/gnome-settings-daemon

(gnome-settings-daemon:6635): GnomeDesktop-WARNING **: could not get output property for default, rc: 15

(gnome-settings-daemon:6635): Gtk-WARNING **: gtk_window_set_wmclass: shouldn't set wmclass after window is realized!

(gnome-settings-daemon:6635): GnomeDesktop-WARNING **: could not get output property for default, rc: 15

(gnome-settings-daemon:6635): power-plugin-WARNING **: not connected

(gnome-settings-daemon:6635): GnomeDesktop-WARNING **: could not get output property for default, rc: 15

(gnome-settings-daemon:6635): GnomeDesktop-WARNING **: could not get output property for default, rc: 15

(gnome-settings-daemon:6635): GnomeDesktop-WARNING **: could not get output property for default, rc: 15

(gnome-settings-daemon:6635): GnomeDesktop-WARNING **: could not get output property for default, rc: 15

** (gnome-settings-daemon:6635): WARNING **: You can only run one xsettings manager at a time; exiting

** (gnome-settings-daemon:6635): WARNING **: Unable to start xsettings manager: Could not initialize xsettings manager.

(gnome-settings-daemon:6635): GLib-GIO-CRITICAL **: Settings schema 'org.gnome.totem.plugins.jamendo' is not installed

[1315124129,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application

(gnome-settings-daemon:6635): media-keys-plugin-WARNING **: Grab failed for some keys, another application may already have access the them.

** (gnome-settings-daemon:6635): WARNING **: Name taken or bus went away - shutting down

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.