apport-gtk crashed with SIGSEGV

Bug #1754887 reported by Péter Prőhle
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

This is a fork of the compound "Bug 1754877",

see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1754877

This fork will be devoted to the "apport-gtk crashed with SIGSEGV" part of the compound bug 1754877, and the other fork parallel to this will contain to the original XZGV + Xorg issue.

Due to the original issue (see bug 1754877) I usually reboot before any bug report possibility shows up, or even I do not login before the reboot.

After reboot, the bug report possibility shows up earlier, than my firefox is started.

Due to the original compound bug, I always get at least two bug report possibilities in parallel.

When I try to answer the first immediately, and when this process arrives to that point, where the apport program tries to open the bugs.lunchpad.net for me, then I can see the ICON of firefox for a short second only in the left icon bar, and then it disapperas, and I get NO firefox at all.

Then, when I open the firefox, and AFTER THIS OPENING I handle the other, second apport window waiting for me already since the beginnings, then it already can simply open a tab in the running firefox for me to continue the bug report there.

My feeling is, that "apport-gtk crashed with SIGSEGV" belongs to the unsuccesful firefox opening, since the first bug report usually disappears.

Whenever I try to reproduce the other "XZGV + Xorg issue", and the firefox is NOT opened IN ADVANCE,then I have an unsuccessful firefox opening experience with apport program: that report trial dies out, disappears.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: apport-gtk 2.20.8-0ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Mar 10 19:58:35 2018
ExecutablePath: /usr/share/apport/apport-gtk
ExecutableTimestamp: 1518540671
InstallationDate: Installed on 2017-07-13 (240 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterpreterPath: /usr/bin/python3.6
JournalErrors:
 -- Logs begin at Fri 2018-03-09 12:38:41 CET, end at Sat 2018-03-10 20:13:45 CET. --
 Mar 10 19:59:48 pc56 spice-vdagent[1675]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
 Mar 10 19:59:48 pc56 pulseaudio[1723]: [pulseaudio] pid.c: Daemon already running.
 Mar 10 20:00:13 pc56 pulseaudio[1521]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcCwd: /home/prohlep
Python3Details: /usr/bin/python3.6, Python 3.6.4+, 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: 0x7f19de99b5a9: mov (%rbx),%rdi
 PC (0x7f19de99b5a9) 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-03-09 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Péter Prőhle (prohlep) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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
Revision history for this message
Péter Prőhle (prohlep) wrote :

"Comment here only if you think the duplicate status is wrong.", OK I do it.

Because that bug is "Crash displayed after logging in.".

And this bug is: apport-gtk crash IF no running firefox, and the apport wants to brig me to bugs.lunchpad.net to continue and finish the bug report.

The resulting end is the same: "apport-gtk crashed with SIGSEGV",

but the situation, context and reason is really different, hence it seems to be a different problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.