compiz crashed with SIGSEGV in gdu_device_get_object_path()

[Petr]

an error occurred while trying to activate a second area in Nautilus after copying the files from external drive

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
ApportVersion: 1.94.1-0ubuntu1
Architecture: i386
CheckboxSubmission: ff2c2e6b3043a8e3c69e5359a28a8379
CheckboxSystem: 9c26adf6eed2f681ba41f94dd24c07e4
CrashCounter: 1
Date: Fri Mar 9 22:29:56 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x70ec8f4 <gdu_device_get_object_path+4>: mov 0xc(%eax),%eax
 PC (0x070ec8f4) 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: Upgraded to precise on 2012-03-08 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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.