[xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()

[Erick Brunzell]

I got this crash report after installing 'gnome-panel', 'indicator-applet',& 'indicator-applet-session', then logging out, choosing classic (no effects) and initially logging into the classic DE. This was a fresh and fully updated Ubuntu 20120413 i386 installation.

Possibly a duplicate of bug 968198 but certainly different circumstances leading up to it so I wanted to allow apport to collect info.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.4.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
Date: Fri Apr 13 23:02:38 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120413)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb4795913: mov (%eax),%eax
 PC (0xb4795913) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
 g_cclosure_marshal_VOID__STRINGv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #963704, 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.

[Erick Brunzell (lbsolost)]

Bug 963704 must either be marked private or it doesn't exist.