unity-2d-shell crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity-2d (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Not sure what caused this crash, but it happens intermittently and can only be fixed by 'killall unity-2d-panel', which I type into an available terminal window if possible. Otherwise, the panel is totally unresponsive.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.14.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-63-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CrashCounter: 1
Date: Thu Jun 19 15:33:28 2014
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: unity-2d-shell
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f1169989082: testb $0x4,(%rbx)
PC (0x7f1169989082) ok
source "$0x4" ok
destination "(%rbx)" (0x2fa0000003d) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: unity-2d-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| John Pye (jdpipe) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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 #936560, 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.