apport-gtk crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu 17.10
Release: 17.10
apport:
Installed: 2.20.7-0ubuntu3.7
Candidate: 2.20.7-0ubuntu3.7
Version table:
*** 2.20.7-0ubuntu3.7 500
500 http://
500 http://
500 http://
500 http://
100 /var/lib/
2.
500 http://
500 http://
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: apport-gtk 2.20.7-0ubuntu3.7
ProcVersionSign
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Mar 23 14:24:50 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/share/
ExecutableTimes
InstallationDate: Installed on 2018-03-17 (5 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterpreterPath: /usr/bin/python3.6
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
ProcCwd: /home/marc
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /home/marc/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/home/marc/Error: command ['which', 'python'] failed with exit code 1:": "/home/marc/Error: command ['which', 'python'] failed with exit code 1:", unpackaged
SegvAnalysis:
Segfault happened at: 0x7f8a2469f659: mov (%rbx),%rdi
PC (0x7f8a2469f659) 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/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: apport-gtk crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2018-03-17 (5 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 #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.