apport-gtk crashed with SIGSEGV in gdk_pixbuf_composite()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apport (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
hm
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-gtk 1.94.1-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-18-generic x86_64
ApportLog:
ERROR: apport (pid 9713) Mon Mar 12 01:01:32 2012: called for pid 9706, signal 11
ERROR: apport (pid 9713) Mon Mar 12 01:01:32 2012: script: /usr/share/
ERROR: apport (pid 9713) Mon Mar 12 01:01:32 2012: is_closing_
ERROR: apport (pid 9713) Mon Mar 12 01:01:36 2012: wrote report /var/crash/
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 12 01:01:32 2012
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
SegvAnalysis:
Segfault happened at: 0x7fd881141981: mov %al,(%rdx)
PC (0x7fd881141981) ok
source "%al" ok
destination "(%rdx)" (0x7fd87b0ddd70) in non-writable VMA region: 0x7fd87836a000-
SegvReason: writing VMA /usr/share/
Signal: 11
SourcePackage: apport
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
gdk_pixbuf_
ffi_call_unix64 () from /usr/lib/
Title: apport-gtk crashed with SIGSEGV in gdk_pixbuf_
UpgradeStatus: Upgraded to precise on 2011-12-10 (92 days ago)
UserGroups:
| Timo Witte (spacefish) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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.