apport-gtk crashed with SIGSEGV in gdk_pixbuf_composite()

[Steve Langasek]

Window never showed up, I got this crash instead. Obviously the window worked the *second* time though, because I was able to file this bug report. ;)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-gtk 1.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CheckboxSubmission: 017452a27eca3c8b498abbfa5ef91db9
CheckboxSystem: ecaaad6fa1e0799a0aa1126bf620f39e
Date: Thu Feb 23 09:36:29 2012
ExecutablePath: /usr/share/apport/apport-gtk
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1ce1bb2981: mov %al,(%rdx)
 PC (0x7f1ce1bb2981) ok
 source "%al" ok
 destination "(%rdx)" (0x7f1cdb7a5eb4) in non-writable VMA region: 0x7f1cdb69d000-0x7f1cdb82e000 r--p /usr/share/icons/Human/icon-theme.cache
SegvReason: writing VMA /usr/share/icons/Human/icon-theme.cache
Signal: 11
SourcePackage: apport
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
 gdk_pixbuf_composite () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: apport-gtk crashed with SIGSEGV in gdk_pixbuf_composite()
UpgradeStatus: Upgraded to precise on 2011-11-08 (106 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src

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