compiz crashed with SIGSEGV in gdu_device_get_object_path()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
compiz crashed while I was away. When I returned I had to unlock the screen. Then the system prompted me with the compiz crash dialog.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-17-generic i686
NonfreeKernelMo
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sun Mar 11 17:15:20 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x65648f4 <gdu_device_
PC (0x065648f4) ok
source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
gdu_device_
gdu_pool_
gdu_pool_new () from /usr/lib/
unity:
unity:
Title: compiz crashed with SIGSEGV in gdu_device_
UpgradeStatus: Upgraded to precise on 2012-03-10 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #916892, 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.