Apport should not just silently fail when it detects the specific crash report has already been uploaded

Bug #1599295 reported by Wise Melon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Apport
Invalid
Undecided
Unassigned
apport (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have recently been having some trouble with Apport, I asked it to submit a crash report however there was a problem and it never launched the browser page. Now every time I try to manually submit the .crash file I get an error saying that the crash report has been already submitted (this is logged in syslog and not anywhere obvious).

When I use the GUI, and when I use the apport-cli program and ask it to submit a report now on the matter it just silently exists without telling me anything. So how am I even meant to know what the URL is that it has been submitted to?

So I think that Apport should really not just silently fail and should instead tell the user that the crash has already been submitted and then actually give them the URL to get to it because otherwise I don't know how one is expected to find it unless they get the Apport's signature generator working manually or something.

I am running Ubuntu GNOME 16.04 with GNOME 3.20.

Tags: xenial
Revision history for this message
Wise Melon (wise-melon-deactivatedaccount) wrote :

Related: Bug #1599297

Jeremy Bícha (jbicha)
no longer affects: ubuntu-gnome
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Submitting an error is not supposed to “launch a browser page”. It hasn’t done that, for release versions of Ubuntu, for four years now. And you know that it did not “silently fail”, because, as you stated, trying to resubmit it manually results in “an error saying that the crash report has been already submitted”. So it had already succeeded.

You can access a linked list of error reports from System Settings > Security & Privacy > Diagnostics > Show Previous Reports.

Changed in apport:
status: New → Invalid
Changed in apport (Ubuntu):
status: New → Invalid
Revision history for this message
Wise Melon (wise-melon-deactivatedaccount) wrote :

Really? Well, I'm certain that it always has done for me... So many times have I had it upload data to LP and where the error is set as the title for the report.

Isn't this https://bugs.launchpad.net/ubuntu/+source/gnome-photos/+bug/1568043 what normally should happen? Or when does this happen and when does it just submit it somewhere else? Also, where exactly did it submit my report to? Shouldn't it have asked at least for my comment on exactly what I was doing at the time as the crash dump may not always be enough?

Where can I access previous reports on Ubuntu GNOME? They don't seem to be in the same place. In fact I don't remember ever seeing them in the gnome-control-center.

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.