apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Running in oracle box
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: apport-gtk 2.19.4-0ubuntu2
ProcVersionSign
Uname: Linux 4.4.0-2-generic x86_64
ApportLog:
ERROR: apport (pid 3768) Fri Feb 5 14:16:58 2016: called for pid 1926, signal 11, core limit 0
ERROR: apport (pid 3768) Fri Feb 5 14:16:58 2016: script: /usr/share/
ERROR: apport (pid 3768) Fri Feb 5 14:16:59 2016: is_closing_
ERROR: apport (pid 3768) Fri Feb 5 14:17:07 2016: wrote report /var/crash/
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CrashReports:
640:0:
640:0:
640:0:
600:0:
Date: Fri Feb 5 14:16:58 2016
ExecutablePath: /usr/share/
InstallationDate: Installed on 2016-01-11 (25 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160105)
InterpreterPath: /usr/bin/python3.5
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
ProcEnviron:
SHELL=/bin/bash
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x7f205e401df0 <gtk_widget_
PC (0x7f205e401df0) ok
source "(%r14)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
gtk_widget_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
gtk_event_
Title: apport-gtk crashed with SIGSEGV in gtk_widget_
UpgradeStatus: No upgrade log present (probably fresh install)
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 #1539995, 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.