Bug reports after segmentation fault are never generated

Bug #1505368 reported by Karl-Philipp Richter
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After `apport` recognizes a segmentation fault it displays a dialog which allows to close or restart the application and contains a checkbox which offers the option to file a bug online. Even if the box is checked no online form to open a new bug report is opened in the browser (as described on https://wiki.ubuntu.com/Apport).

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apport 2.17.2-0ubuntu1.5
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 12 21:29:18 2015
InstallationDate: Installed on 2015-09-14 (27 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportLog:
 ERROR: apport (pid 4083) Fri Feb 17 22:37:25 2017: called for pid 19798, signal 6, core limit 0
 ERROR: apport (pid 4083) Fri Feb 17 22:37:25 2017: executable: /usr/lib/gnome-terminal/gnome-terminal-server (command line "/usr/lib/gnome-terminal/gnome-terminal-server")
 ERROR: apport (pid 4083) Fri Feb 17 22:37:25 2017: debug: session gdbus call: (true,)

 ERROR: apport (pid 4083) Fri Feb 17 22:37:39 2017: wrote report /var/crash/_usr_lib_gnome-terminal_gnome-terminal-server.1000.crash
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2015-12-12 (433 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl
Package: apport 2.20.3-0ubuntu8.2
PackageArchitecture: all
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Tags: yakkety
Uname: Linux 4.8.0-37-generic x86_64
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (123 days ago)
UserGroups: adm autopilot bumblebee cdrom dip libvirt libvirtd lp lpadmin plugdev sambashare saned sudo vboxusers
_MarkForUpload: True

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :
Revision history for this message
Lysenko Denis (pharmasolin) wrote :

Tested in 15.04, not confirmed. Tested with "apport-bug -w" in terminal on calculator, it's collected data and opened for me browser to create report with all data.

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :
Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

"Manual"/"Explicit" bug reporting with `ubuntu-bug` or `apport-bug` works as expected (browser window is opened and data is processed remotely after collecting it locally). The issue concerns issues which have been detected by `apport` automatically (e.g. after segmentation fault) only.

description: updated
Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

I figured that I can reproduce this issue by invoking ``python3 `which mysql-workbench` `` (where `which mysql-workbench` refers to a shell script). The `apport` dialog is displayed and offers to close or restart the application as well as the option to file a bug report. Both closing and restarting the application with the option checked brings no result.

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

I proposed provision of test crash application in a PPA at https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1506768 in order to facilitate debugging issues like this one.

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

This is still an issue in Ubuntu 16.10/2.20.3-0ubuntu8 and has been in all Ubuntu versions in between.

It is hard to tell what is supposed to happen because apport doesn't give any feedback. I guess, a browser is supposed to open where the report can be completed _or_ the report is uploaded automatically in which case I didn't managed to find it in the last cases where I tried to search it with the title displayed in the `apport` dialog or the list of recent bugs of the affected application on launchpad.net. I also see no entry in the list of reports on my launchpad.net profile sorted by age.

tags: added: apport-collected yakkety
description: updated
Revision history for this message
Karl-Philipp Richter (krichter722) wrote : CrashReports.txt

apport information

Revision history for this message
Karl-Philipp Richter (krichter722) wrote : Dependencies.txt

apport information

Revision history for this message
Karl-Philipp Richter (krichter722) wrote : JournalErrors.txt

apport information

Revision history for this message
Karl-Philipp Richter (krichter722) wrote : ProcEnviron.txt

apport information

Revision history for this message
Karl-Philipp Richter (krichter722) wrote : upstart.apport.override.txt

apport information

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

Can you reproduce the problem with `ubuntu-bug /var/crash/[crash file]`?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

Changed in apport (Ubuntu):
status: New → Incomplete
Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

This is still an issue with 2.20.7 of Ubuntu 17.10. I can perform an `apport-collect` which works.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry, it's just that you only mentioned Ubuntu 15.04 and 16.10 above. If you have a problem with 17.10 then please report it from 17.10.

That aside, I think this might be best explained by bug 994921. Annoyingly, normal bug reports get blocked after a release occurs.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for apport (Ubuntu) because there has been no activity for 60 days.]

Changed in apport (Ubuntu):
status: Incomplete → Expired
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.