apport-gtk crashed with SIGSEGV in _gtk_icon_helper_get_storage_type()

[Rainer Rohde]

Just crashed after logging in...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-gtk 1.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Tue Feb 21 13:41:07 2012
ExecutablePath: /usr/share/apport/apport-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc3b3ac7a60: mov 0x18(%rdi),%rax
 PC (0x7fc3b3ac7a60) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_image_clear () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_image_set_from_stock () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: apport-gtk crashed with SIGSEGV in gtk_image_clear()
UpgradeStatus: Upgraded to precise on 2012-01-31 (21 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 _gtk_icon_helper_get_storage_type (self=0x0) at /build/buildd/gtk+3.0-3.3.14/./gtk/gtkiconhelper.c:482
 gtk_image_reset (image=0x235e350) at /build/buildd/gtk+3.0-3.3.14/./gtk/gtkimage.c:1430
 gtk_image_clear (image=0x235e350) at /build/buildd/gtk+3.0-3.3.14/./gtk/gtkimage.c:1486
 gtk_image_set_from_stock (image=0x235e350, stock_id=<optimized out>, size=GTK_ICON_SIZE_DIALOG) at /build/buildd/gtk+3.0-3.3.14/./gtk/gtkimage.c:884
 ffi_call_unix64 () at ../src/x86/unix64.S:75

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.