gnome-settings-daemon crashed with SIGSEGV in g_settings_backend_changed()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Just doing normal work over 13.10beta. My system did not crash, but it did request me to file this report.
Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10
$ apt-cache policy gnome-settings-
gnome-settings-
Installed: 3.8.5-0ubuntu6
Candidate: 3.8.5-0ubuntu6
Version table:
*** 3.8.5-0ubuntu6 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-settings-
ProcVersionSign
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Mon Oct 7 02:02:35 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2012-11-14 (326 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7f3931472b7c: mov (%rax,%r13,1),%rax
PC (0x7f3931472b7c) ok
source "(%rax,%r13,1)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-
StacktraceTop:
?? () from /usr/lib/
g_settings_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-settings-
UpgradeStatus: Upgraded to saucy on 2013-09-25 (12 days ago)
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 #1235982, 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.