apport-gtk crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hello,
I do not know what happened.
Regards,
--
Cristian Aravena Romero (caravena)
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: apport-gtk 2.20.10-0ubuntu1
Uname: Linux 4.16.7-
ApportLog:
ERROR: apport (pid 3718) Fri May 11 15:02:22 2018: called for pid 3716, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 3718) Fri May 11 15:02:22 2018: script: /usr/share/
ERROR: apport (pid 3718) Fri May 11 15:02:22 2018: is_closing_
ERROR: apport (pid 3718) Fri May 11 15:02:31 2018: wrote report /var/crash/
ERROR: apport (pid 8793) Fri May 11 15:44:18 2018: host pid 8791 crashed in a separate mount namespace, ignoring
ApportVersion: 2.20.10-0ubuntu1
Architecture: amd64
Date: Fri May 11 15:02:22 2018
ExecutablePath: /usr/share/
ExecutableTimes
InstallationDate: Installed on 2017-10-13 (210 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
InterpreterPath: /usr/bin/python3.6
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
ProcCwd: /var/crash
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15~rc1-1
SegvAnalysis:
Segfault happened at: 0x7f2dde92e799: mov (%rbx),%rdi
PC (0x7f2dde92e799) 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:
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
Title: apport-gtk crashed with SIGSEGV
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 #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.