apport-gtk crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Automatic crash report.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: apport-gtk 2.20.5-0ubuntu4
ProcVersionSign
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CrashReports:
640:1000:
640:1000:
CurrentDesktop: Unity:Unity7
Date: Mon Jun 5 13:47:29 2017
ExecutablePath: /usr/share/
InstallationDate: Installed on 2017-04-29 (37 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170428)
InterpreterPath: /usr/bin/python3.5
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
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/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: apport-gtk crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.