apport-gtk crashed with SIGSEGV

Bug #1740165 reported by wxdf
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

???

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: apport-gtk 2.20.8-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Dec 26 18:59:55 2017
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2014-09-01 (1212 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f8ee263a969: mov (%rbx),%rdi
 PC (0x7f8ee263a969) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: apport-gtk crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2017-12-18 (7 days ago)
UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev nopasswdlogin plugdev sambashare scanner sudo tape video

Revision history for this message
wxdf (hboehme90) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1552577, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.