apport-gtk crashed with SIGSEGV

Bug #1695887 reported by Hans Joachim Desserud on 2017-06-05
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Undecided
Unassigned

Bug Description

Automatic crash report.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: apport-gtk 2.20.5-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CrashReports:
 640:1000:121:6729614:2017-06-05 13:47:57.407585382 +0200:2017-06-05 13:47:58.407585382 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
 640:1000:121:7583396:2017-06-05 13:47:08.600048065 +0200:2017-06-05 13:47:09.600048065 +0200:/var/crash/_usr_bin_compiz.1000.crash
CurrentDesktop: Unity:Unity7
Date: Mon Jun 5 13:47:29 2017
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2017-04-29 (37 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170428)
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
SegvAnalysis:
 Segfault happened at: 0x7f30f299d909: mov (%rbx),%rdi
 PC (0x7f30f299d909) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Hans Joachim Desserud (hjd) wrote :

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  Edit
Everyone can see this information.

Other bug subscribers