compiz crashed with SIGSEGV in gdu_device_get_object_path()

[Jean-Baptiste Lallement]

Crashed at the end of a usb-creator run

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.93-0ubuntu2
Architecture: i386
Date: Wed Feb 29 22:54:32 2012
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1330015289
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120228.1)
ProcCmdline: compiz
ProcCwd: /home/ubuntu
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb3cc68f4 <gdu_device_get_object_path+4>: mov 0xc(%eax),%eax
 PC (0xb3cc68f4) 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::OnVolumeAdded(_GVolumeMonitor*, _GVolume*, unity::launcher::DeviceLauncherSection*) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in gdu_device_get_object_path()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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.