gnome-settings-daemon crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: gnome-settings-
I was using synaptic package manager to download four updates to Ubuntu 11.4 when this crash occurred. My Eee 901 system appears flaky at present and their could be a problem from an un-installed programme (Ubuntu Tweek) previously removed by the upgrade process. as the window still rolls up when clicking on the top title bare area which is no longer visible in classic mode.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-settings-
ProcVersionSign
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
CheckboxSubmission: 64dc7f1460e0380
CheckboxSystem: b62ae224500b03a
Date: Sat Feb 26 11:45:16 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x51eae6: movsbl (%eax),%eax
PC (0x0051eae6) ok
source "(%eax)" (0x00000001) 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/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-settings-
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (nautilus:1375): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
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 #725972, 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.