compiz crashed with SIGSEGV in DeviceLauncherIcon::UpdateVisibility()

[Fabien Tassin]

Binary package hint: unity

using nautilus, trying to open an sftp:// link, kaboom

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 x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Mar 21 09:14:43 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/tcsh
SegvAnalysis:
 Segfault happened at: 0x7f6fdb27f3c0 <_ZN18DeviceLauncherIcon16UpdateVisibilityEv+112>: mov 0x2d8(%rbx),%rdi
 PC (0x7f6fdb27f3c0) ok
 source "0x2d8(%rbx)" (0x000002d8) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 DeviceLauncherIcon::UpdateVisibility() () from /usr/lib/compiz/libunityshell.so
 g_closure_invoke (closure=0x24f7830, return_value=0x0, n_param_values=2, param_values=0x4a43800, invocation_hint=0x7fffb8ec85e0) at /build/buildd/glib2.0-2.28.3/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0x245f900, emission_return=0x0, instance_and_params=0x4a43800) at /build/buildd/glib2.0-2.28.3/./gobject/gsignal.c:3252
 g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=<value optimized out>) at /build/buildd/glib2.0-2.28.3/./gobject/gsignal.c:2983
 g_signal_emit_by_name (instance=0x245f900, detailed_signal=0x7f6fe7ed0632 "mount-added") at /build/buildd/glib2.0-2.28.3/./gobject/gsignal.c:3077
Title: compiz crashed with SIGSEGV in DeviceLauncherIcon::UpdateVisibility()
UpgradeStatus: Upgraded to natty on 2009-07-28 (600 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 #739083, 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.