apport-gtk crashed with SIGSEGV in gtk_image_clear()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have no idea what I did to cause this.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-gtk 1.94.1-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sun Mar 11 06:04:26 2012
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120125)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
SegvAnalysis:
Segfault happened at: 0x7f521de1b850: mov 0x18(%rdi),%rax
PC (0x7f521de1b850) 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-02-17 (22 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.