compiz crashed with SIGSEGV in DeviceLauncherIcon::UpdateVisibility()

[Aleh]

Binary package hint: unity

Distributor ID: Ubuntu
Description: Ubuntu Natty (development branch)
Release: 11.04
Codename: natty
man 2.5.9
???
???

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.6.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.36-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: wl
Architecture: i386
CheckboxSubmission: 112c7360a6aec96825b93850080040b1
CheckboxSystem: 21aa6c17e1fc79cc65eed2169d1b6afc
CrashCounter: 1
Date: Sun Mar 20 14:30:43 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=ru_RU:en
 PATH=(custom, user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8a63a48 <_ZN18DeviceLauncherIcon16UpdateVisibilityEv+136>: mov 0x1ac(%esi),%eax
 PC (0x08a63a48) ok
 source "0x1ac(%esi)" (0x000001ac) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 DeviceLauncherIcon::UpdateVisibility() () from /usr/lib/compiz/libunityshell.so
 DeviceLauncherSection::OnMountAdded(_GVolumeMonitor*, _GMount*, DeviceLauncherSection*) () from /usr/lib/compiz/libunityshell.so
 g_cclosure_marshal_VOID__OBJECT () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: compiz crashed with SIGSEGV in DeviceLauncherIcon::UpdateVisibility()
UpgradeStatus: Upgraded to natty on 2011-03-18 (1 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #737318, 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.