[Bug 1232419] [NEW] [xsettings]: gnome-settings-daemon crashed with SIGSEGV in notify_have_shell()

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

No idea what this relates to, but the crash was reported on a reboot,
and appeared just after launching the Display settings UI.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-settings-daemon 3.8.5-0ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sat Sep 28 00:08:59 2013
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationDate: Installed on 2013-08-15 (43 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha i386 (20130626)
MarkForUpload: True
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0xb5a5d12a:	mov    (%eax),%eax
 PC (0xb5a5d12a) 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/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in ffi_call_SYSV()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: gnome-settings-daemon (Ubuntu)
     Importance: High
         Status: Confirmed


** Tags: apport-crash i386 patch saucy third-party-packages xsettings
-- 
[xsettings]: gnome-settings-daemon crashed with SIGSEGV in notify_have_shell()
https://bugs.launchpad.net/bugs/1232419
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.