apport-gtk sigfault in libgtk-3

Bug #1720116 reported by Cliff Carson on 2017-09-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
High
Unassigned

Bug Description

Daily notification of system error and request to report it but nothing get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us usually no crash dump generated.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 -0400:2017-09-22 05:36:27.979332060 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash
CurrentDesktop: GNOME-Classic:GNOME
Date: Thu Sep 28 06:54:23 2017
InstallationDate: Installed on 2017-07-24 (65 days ago)
InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

Cliff Carson (ccarson1) wrote :
dino99 (9d9) wrote :
Cliff Carson (ccarson1) wrote :

This error has shown up in last week or so. Been running Artful for over a month. Usually on every boot will open a command shell and update/upgrade for the latest updates then open chrome. By then the popup box shows up indicating the an error had occurred and asking if it should be reported. After hitting the Yes button nothing else happens.

Have a syslog snippet and I think a corresponding crash from 9/22 if it would help.

Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in apport (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Cliff Carson (ccarson1) wrote :

Unable to run apport-retrace. Get the following

cliff@cliffps:~/tmp$ apport-retrace _usr_share_apport_apport-gtk.0.crash
ERROR: report file does not contain one of the required fields: Package

First part of the crash file

ProblemType: Crash
Architecture: amd64
Date: Fri Sep 22 05:36:27 2017
DistroRelease: Ubuntu 17.10
ExecutablePath: /usr/share/apport/apport-gtk
ExecutableTimestamp: 1504050301
InterpreterPath: /usr/bin/python3.6
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcCwd: /root
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcMaps:

dino99 (9d9) wrote :

apport-retrace needs both: python-cffi-backend & python3-cffi-backend installed to work

Cliff Carson (ccarson1) wrote :

Both of these are installed

python-cffi-backend is already the newest version (1.9.1-2build2).
python-cffi-backend set to manually installed.
python3-cffi-backend is already the newest version (1.9.1-2build2).
python3-cffi-backend set to manually installed.

Brian Murray (brian-murray) wrote :

Would you mind uploading the apport-gtk.0.crash file to the bug report? I'd like to take a look at it and retrace it.

Cliff Carson (ccarson1) wrote :

Attaching the syslog text showing the sigfault and I think the corresponding crash file.

Cliff Carson (ccarson1) wrote :

Reviewed all the available syslogs and found 2-3 of the apport-gtk failures per day from 9/22 to 9/27. Only one failure on 9/28 and none on 9/29. Had other problems on 9/30 which required a re-install at the 9/29 build level. Will add a comment if this problem reappears.

Changed in apport (Ubuntu):
status: Incomplete → New
Brian Murray (brian-murray) wrote :

Looking at the apport log file again this looks suspect:

ERROR: apport (pid 2661) Thu Sep 28 06:51:20 2017: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment

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

Other bug subscribers

Remote bug watches

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