apport-gtk crashed with SIGSEGV in gtk_icon_source_set_pixbuf()

[Dmitry Shachnev]

Binary package hint: apport

This happened while I was testing the oneiric daily LiveCD.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: apport-gtk 1.21-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-0.1-generic 3.0.0-rc2
Uname: Linux 3.0-0-generic i686
Architecture: i386
CrashCounter: 1
CrashReports:
 600:999:999:785500:2011-06-16 09:21:07.000000000 +0000:2011-06-16 09:21:08.000000000 +0000:/var/crash/_usr_bin_gnome-power-manager.999.crash
 600:999:999:9924241:2011-06-16 09:22:26.000000000 +0000:2011-06-16 09:22:27.000000000 +0000:/var/crash/_usr_share_apport_apport-gtk.999.crash
 600:999:999:1596840:2011-06-16 09:22:07.000000000 +0000:2011-06-16 09:22:08.000000000 +0000:/var/crash/_usr_bin_gnome-control-center.999.crash
Date: Thu Jun 16 09:22:21 2011
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110615)
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x106b429 <gtk_icon_source_set_pixbuf+57>: cmp %eax,(%edx)
 PC (0x0106b429) ok
 source "%eax" ok
 destination "(%edx)" (0x00000006) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 gtk_icon_source_set_pixbuf () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
Title: apport-gtk crashed with SIGSEGV in gtk_icon_source_set_pixbuf()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 797498, so it 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.