compiz crashed with SIGSEGV in unity::hud::HudIconTextureSource::ColorForIcon()

[Christian Hauskov]

I was working in Mendeley Desktop 1.5.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.6.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
Uname: Linux 3.2.0-19-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sun Mar 18 16:11:38 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0xb33d73a5 <_ZN5unity3hud20HudIconTextureSource12ColorForIconEP10_GdkPixbuf+37>: mov (%esi),%edx
 PC (0xb33d73a5) ok
 source "(%esi)" (0x29df0ac2) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 unity::hud::HudIconTextureSource::ColorForIcon(_GdkPixbuf*) () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/compiz/libunityshell.so
 unity::IconTexture::IconLoaded(std::string const&, unsigned int, _GdkPixbuf*) () from /usr/lib/compiz/libunityshell.so
 sigc::internal::slot_call3<sigc::bound_mem_functor3<void, unity::IconTexture, std::string const&, unsigned int, _GdkPixbuf*>, void, std::string const&, unsigned int, _GdkPixbuf*>::call_it(sigc::internal::slot_rep*, std::string const&, unsigned int const&, _GdkPixbuf* const&) () from /usr/lib/compiz/libunityshell.so
 unity::IconLoader::Impl::ProcessGIconTask(unity::IconLoader::Impl::IconLoaderTask*) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in unity::hud::HudIconTextureSource::ColorForIcon()
UpgradeStatus: Upgraded to precise on 2012-03-12 (6 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 this software better. This particular crash has already been reported and is a duplicate of bug #957910, 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.