ubuntu 12.04 unity-2d-shell crashed with SIGSEGV while dismount a hard disk filesystem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-2d (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 12.04 Release 12.04 (precise) 64-bit Kernel Linux 3.2.0-23-generic.
While dismount a hard disk filesystem (1TB ext4) unity was blocked for 5 seconds and crashed.
I was not performing other activities.
My system (upgrade of ubuntu 11.10) is updated on 15/04/2012.
Thank you
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.10.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 15 09:28:04 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: unity-2d-shell
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f0c7bf1b04a: testb $0x8,0x20(%r15)
PC (0x7f0c7bf1b04a) ok
source "$0x8" ok
destination "0x20(%r15)" (0x1400002025992e0) 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-31 (14 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(gnome-
(gnome-
(gnome-
(gnome-
gnome-
security vulnerability: | no → yes |
visibility: | private → public |
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.