compiz crashed when an ipod touch is plugged

[grizzo94]

Binary package hint: unity

1)Release:
Description: Ubuntu Natty (development branch)
Release: 11.04
2)Compiaz version: 1:0.9.4-0ubuntu7
Unity Version: 3.6.6-0ubuntu1
4) When I Plug an iPod Touch (3G) compiz crashes and doesn't appear any window of error that lets me to restart compiz.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.6.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.36-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Mon Mar 21 18:49:05 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=it_IT:en
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb4017a48 <_ZN18DeviceLauncherIcon16UpdateVisibilityEv+136>: mov 0x1ac(%esi),%eax
 PC (0xb4017a48) 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-21 (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 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.