apport-gtk crashes with SIGSEGV if invalid DISPLAY given
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Running
DISPLAY=-1 ubuntu-bug somepackage
prints
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Segmentation fault (core dumped)
and apport stops working.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: apport-gtk 2.20.9-0ubuntu7.6
ProcVersionSign
Uname: Linux 5.0.0-15-generic x86_64
ApportLog:
ERROR: apport (pid 5603) Sun Jun 2 01:09:25 2019: called for pid 5601, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 5603) Sun Jun 2 01:09:25 2019: script: /usr/share/
ERROR: apport (pid 5603) Sun Jun 2 01:09:25 2019: debug: session gdbus call: (true,)
ERROR: apport (pid 5603) Sun Jun 2 01:09:28 2019: wrote report /var/crash/
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CrashReports:
640:1000:
664:1000:
640:1000:
600:111:
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 2 01:09:25 2019
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python3.6
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
SegvAnalysis:
Segfault happened at: 0x7fd54c9acff9: mov (%rbx),%rdi
PC (0x7fd54c9acff9) 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: adm cdrom dip fax libvirt libvirtd lpadmin lxd plugdev sambashare sudo users vboxusers
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.