gnome-settings-daemon crashed with SIGSEGV in g_main_context_dispatch()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I called gnome-terminal by typing "term" in fast search. When the terminal popped up, I right-clicked its icon in the launcher with thge intent of pinning it there. For some reason the context menu wasn't clickable. I dragged the terminal window around (it moved very slowly, with a delay relative to the mouse cursor position) a little. Then I right-clicked again, making the stale context menu disappear. Then I right-clicked the icon again, then I selected the "keep program in launcher" option. Shortly after, this crash happened.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Tue Sep 27 23:04:08 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/false
PATH=(custom, no user)
LANGUAGE=
LANG=pt_BR.UTF-8
SegvAnalysis:
Segfault happened at: 0x3135f5d: mov 0x8(%edx),%edx
PC (0x03135f5d) ok
source "0x8(%edx)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
?? () from /lib/i386-
Title: gnome-settings-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
| JCCyC (jccyc1965) wrote | #3 |
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 #860686, 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.