May be several minutes between crash and error message

Bug #1058160 reported by Matthew Paul Thomas on 2012-09-28
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Apport
Medium
Unassigned
apport (Ubuntu)
Undecided
Unassigned

Bug Description

apport 2.5.2-0ubuntu4, Ubuntu Q

1. Cause something to crash in such a way that the crash report is extremely large. Simulate this by putting <https://launchpadlibrarian.net/117663246/_usr_bin_gwibber-service.1000.crash> into /var/crash/.

What happens: An error alert appears after several minutes.

What should happen: An error alert appears after no more than a few seconds.

Currently Apport processes a crash report completely before the error alert appears. It could instead put up the error alert immediately before the report has finished processing, based solely on the process ID. The Details pane of an error alert already includes a spinner if the report hasn't finished processing yet.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Evan (ev) on 2012-11-01
tags: added: whoopsie-daisy
Evan (ev) wrote :

We could send a signal that apport-gtk should be spawned, waiting for a report to appear at a specific path. This is no small change though. It completely alters the current workflow.

Changed in apport:
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers