[xsettings]: gnome-settings-daemon crashed with SIGSEGV in ffi_call_SYSV()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
the bug appears when the system is starting after entering the password and switching to the GUI, without doing something else. I use a second screen together with a laptop. The laptop screen should be always switched off by starting, but the the setting gets always lost and the system starts always with two screens. So I have to change the settings after every system start.
After the bug I can work as usual.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-settings-
ProcVersionSign
Uname: Linux 3.13.0-20-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CrashCounter: 1
CurrentDesktop: GNOME
Date: Wed Apr 2 06:51:57 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-03-19 (13 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha i386 (20140226)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0xb4edc50a: mov (%eax),%eax
PC (0xb4edc50a) 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-
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
ffi_call_SYSV () from /usr/lib/
ffi_call () from /usr/lib/
Title: [xsettings]: gnome-settings-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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 #1273870, 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.