apport-gtk crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apport (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Auto-report. No obvious symptoms.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: apport-gtk 2.20.11-0ubuntu16
ProcVersionSign
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CrashReports:
640:1000:
640:1000:
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Feb 15 10:36:16 2020
ExecutablePath: /usr/share/
ExecutableTimes
InstallationDate: Installed on 2020-02-10 (4 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200210)
InterpreterPath: /usr/bin/python3.8
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
ProcCwd: /home/rodsmith
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
LD_PRELOAD=<set>
SHELL=/bin/bash
Python3Details: /usr/bin/python3.8, Python 3.8.2rc1, python3-minimal, 3.8.0-3
PythonDetails: N/A
SegvAnalysis:
Segfault happened at: 0x7ff43cc357e4: mov 0x18(%rdi),%rax
PC (0x7ff43cc357e4) 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 /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: apport-gtk crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
| Rod Smith (rodsmith) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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.