apport-gtk crashed with SIGSEGV in gtk_image_clear()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
bug showed without any special interaction....
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-gtk 1.94.1-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelMo
ApportLog:
ERROR: apport (pid 3022) Thu Mar 22 09:56:47 2012: called for pid 2692, signal 11
ERROR: apport (pid 3022) Thu Mar 22 09:56:47 2012: script: /usr/share/
ERROR: apport (pid 3022) Thu Mar 22 09:56:47 2012: is_closing_
ERROR: apport (pid 3033) Thu Mar 22 09:56:50 2012: another apport instance is already running, aborting
ERROR: apport (pid 3022) Thu Mar 22 09:56:52 2012: wrote report /var/crash/
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Thu Mar 22 09:56:47 2012
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
TERM=unknown
SegvAnalysis:
Segfault happened at: 0x7ffb27e1c310: mov 0x18(%rdi),%rax
PC (0x7ffb27e1c310) 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/
gtk_image_clear () from /usr/lib/
gtk_image_
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
Title: apport-gtk crashed with SIGSEGV in gtk_image_clear()
UpgradeStatus: Upgraded to precise on 2012-03-13 (9 days ago)
UserGroups:
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 #938090, 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.