gnome-settings-daemon crashed with SIGSEGV in gdk_display_get_event()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Crashed after Firefox's plugin-container (most likely Adobe Flash) started to user 100%+ CPU.
After this crash, the cursor doesn't move.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-
ProcVersionSign
Uname: Linux 3.2.0-5-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CheckboxSubmission: ed5dbdfb54bf504
CheckboxSystem: b633b4f40868d49
Date: Mon Dec 19 12:48:50 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f00d9805ce7: mov 0x10(%rbx),%ecx
PC (0x7f00d9805ce7) ok
source "0x10(%rbx)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
gdk_display_
Title: gnome-settings-
UpgradeStatus: Upgraded to precise on 2011-12-17 (1 days ago)
UserGroups: adm admin cdrom dialout dip lpadmin netdev plugdev sambashare
| Alex Mayorga (alex-mayorga) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
| Alex Mayorga (alex-mayorga) wrote | #3 |
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 #814473, 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.