unity-2d-shell crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity-2d (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
normally, while i move the mouse to the left, the 'vertical bar' appeard, so i can switch the apps. but after a few times, this 'vertical bar' didn't disappear, but just stayed there at the left.
ps: english isn't my mother language, but i hope you know what i said.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.6.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-18-
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sat Mar 10 21:57:02 2012
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick" - Build i386 LIVE Binary 20110422-19:07
ProcCmdline: unity-2d-shell
SegvAnalysis:
Segfault happened at: 0xb6748a25: testb $0x4,(%esi)
PC (0xb6748a25) ok
source "$0x4" ok
destination "(%esi)" (0x40500000) 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: Upgraded to precise on 2012-03-08 (2 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
| yddium (yddium) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-i386-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.