gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After updating 14.04 LTS to 14.10 beta, happened on login. GNOME shell restarted automatically and appears fine after that.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gnome-shell 3.12.2-1ubuntu4
ProcVersionSign
Uname: Linux 3.16.0-18-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Oct 1 10:16:54 2014
DisplayManager: gdm
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-05-12 (506 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f1a7dee1f95: mov %rax,0x50(%r14)
PC (0x7f1a7dee1f95) ok
source "%rax" ok
destination "0x50(%r14)" (0x00000050) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
clutter_
Title: gnome-shell crashed with SIGSEGV in clutter_
UpgradeStatus: Upgraded to utopic on 2014-10-01 (0 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
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 #1374786, 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.