Comment 5 for bug 938707
Revision history for this message
| Evan (ev) wrote Re: [Bug 938707] Re: Hard to see which program crashed for "Internal error" reports | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
On Thu, Feb 23, 2012 at 10:25 PM, Martin Pitt <email address hidden> wrote:
> Before it was much easier for an user to say "ah, that
> program again, already reported or I don't want to", now you need to
> wait for the full data collection first. Bear in mind that in some cases
> this might even involve interactive questions, which sounds like an
> excessively high price for telling you the name of the program.
Hi Martin,
From your perspective and given the solution Matthew presents above,
is it sufficient to make this change and leave the rest of the current
behavior as-is? That is, the UI is hidden and the process spins away
in the background, continuing to collect the additional information
and then quitting. Or would you prefer to see something that
communicates to the thread that it needs to commit suicide at this
point?