compiz crashed with SIGSEGV in SimpleLauncherIcon::SetIconName()

[Cristian Aravena Romero]

Working with chromium+flash(private)... and moment crash compiz.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7
Uname: Linux 3.0.0-6-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Jul 22 22:42:55 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: compiz
ProcEnviron:
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f44082515e1: movdqu (%rdi),%xmm1
 PC (0x7f44082515e1) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 SimpleLauncherIcon::SetIconName(char const*) () from /usr/lib/compiz/libunityshell.so
 BamfLauncherIcon::BamfLauncherIcon(Launcher*, _BamfApplication*, CompScreen*) () from /usr/lib/compiz/libunityshell.so
 LauncherController::OnViewOpened(_BamfMatcher*, _BamfView*, void*) () from /usr/lib/compiz/libunityshell.so
 g_closure_invoke (closure=0x2677a80, return_value=0x0, n_param_values=2, param_values=0x7f43ec153d80, invocation_hint=<value optimized out>) at /build/buildd/glib2.0-2.29.10/./gobject/gclosure.c:773
Title: compiz crashed with SIGSEGV in SimpleLauncherIcon::SetIconName()
UpgradeStatus: Upgraded to oneiric on 2011-07-16 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Susan Cragin (susancragin)]

I updated to linux 3.0.0-7 before the crash. I am also 64-bit

[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 #814619, 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.