apport-gtk crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I am useing ubuntu 20.04
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: apport-gtk 2.20.11-0ubuntu26
ProcVersionSign
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Apr 14 17:02:37 2020
ExecutablePath: /usr/share/
InstallationDate: Installed on 2020-02-08 (65 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
InterpreterPath: /usr/bin/python3.8
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
SegvAnalysis:
Segfault happened at: 0x7fabaa45e2f4: mov 0x18(%rdi),%rax
PC (0x7fabaa45e2f4) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rax" 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 focal on 2020-04-12 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
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 #1842439, 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.