compiz crashed with SIGSEGV in gdk_pixbuf_get_width()

[Liam McDermott]

Was running a fullscreen game in Wine, pressed 'Alt' key, which attempted to trigger the HUD (or some overlay thingamjigger). Getting angry because it was interrupting my game, I bashed Esc and several other keys and noticed the overlay thingamjigger was not responding: it wouldn't go away and neither did any of the other keys I pressed register in the text box.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 23 17:14:50 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120221)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f375100236e <gdk_pixbuf_get_width+14>: mov (%rbx),%rdx
 PC (0x7f375100236e) ok
 source "(%rbx)" (0xa614ea614ea614ea) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 gdk_pixbuf_get_width () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
 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
 unity::IconLoader::Impl::ProcessGIconTask(unity::IconLoader::Impl::IconLoaderTask*) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in gdk_pixbuf_get_width()
UpgradeStatus: Upgraded to precise on 2012-02-23 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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