apport-gtk crashed with SIGSEGV

Bug #1758519 reported by Ertan Günay on 2018-03-24
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Undecided
Unassigned

Bug Description

When I connect with xrdp from remote computer, this error happens mostly.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: apport-gtk 2.20.8-0ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Mar 24 12:12:11 2018
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2017-10-07 (168 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171006)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
SegvAnalysis:
 Segfault happened at: 0x7f194d3a55a9: mov (%rbx),%rdi
 PC (0x7f194d3a55a9) 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/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: apport-gtk crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2018-02-24 (27 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video

Ertan Günay (ergunay) wrote :

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers