compiz crashed with SIGSEGV in gdu_device_get_object_path()

Bug #938952 reported by Daniel Hahler
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Duplicate of bug 926845 ?

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Wed Feb 22 20:42:40 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0xb2d5b8f4 <gdu_device_get_object_path+4>: mov 0xc(%eax),%eax
 PC (0xb2d5b8f4) 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_get_object_path () from /usr/lib/i386-linux-gnu/libgdu.so.0
 gdu_pool_new_for_address () from /usr/lib/i386-linux-gnu/libgdu.so.0
 gdu_pool_new () from /usr/lib/i386-linux-gnu/libgdu.so.0
 unity::launcher::DeviceLauncherIcon::DeviceLauncherIcon(_GVolume*) () from /usr/lib/compiz/libunityshell.so
 unity::launcher::DeviceLauncherSection::PopulateEntries(unity::launcher::DeviceLauncherSection*) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in gdu_device_get_object_path()
UpgradeStatus: Upgraded to precise on 2011-12-16 (68 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers

Revision history for this message
Daniel Hahler (blueyed) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.