compiz crashed with SIGSEGV in unity::dash::ResultRendererTile::IconLoaded()

[Carla Sella]

I had just logged on to my account after a reboot.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.12.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
Date: Wed Sep 7 13:33:13 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: compiz
ProcCwd: /home/charlie
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f7f82de4f11: mov (%r15),%rdx
 PC (0x7f7f82de4f11) ok
 source "(%r15)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/libdee-1.0.so.1
 ?? () from /usr/lib/libdee-1.0.so.1
 unity::dash::ResultRendererTile::IconLoaded(char const*, unsigned int, _GdkPixbuf*, std::string, unity::dash::Result&) () from /usr/lib/compiz/libunityshell.so
 sigc::internal::slot_call3<sigc::bind_functor<-1, sigc::bound_mem_functor5<void, unity::dash::ResultRendererTile, char const*, unsigned int, _GdkPixbuf*, std::string, unity::dash::Result&>, std::string, unity::dash::Result, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void, char const*, unsigned int, _GdkPixbuf*>::call_it(sigc::internal::slot_rep*, char const* const&, unsigned int const&, _GdkPixbuf* const&) () from /usr/lib/compiz/libunityshell.so
 IconLoader::ProcessURITaskReady(IconLoader::IconLoaderTask*, char*, unsigned long) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in unity::dash::ResultRendererTile::IconLoaded()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare 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 #842784, 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.