Bug 168959 - KCrash should have a timeout
Summary: KCrash should have a timeout
Status: RESOLVED DUPLICATE of bug 126073
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-12 09:29 UTC by Jose
Modified: 2008-10-26 15:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jose 2008-08-12 09:29:37 UTC
Version:            (using KDE 4.1.0)
Installed from:    Ubuntu Packages
OS:                Linux

A lot of times, I end my session and choose to shutdown the computer, then I leave the computer unattended while it is shutting down the processes. The problem is that sometimes a program crashes on exit and the kcrash dialog remains on the screen, stopping the shutdown process. Then I come back to my computer later (maybe even a few days later) just to find that it didn't shutdown just because that crash screen that could have been automatically closed.
I think it should be some kind of timeout (maybe only on logout) for kcrash messages so they are closed automatically in X seconds and shown again in the next session saying that application Y crashed in the last session (and to show the bug reporting tool and so on). That way, one can leave the computer unattended on logout and be sure that it will be off in a few seconds and that you are not going to find it on next time you want to turn on your computer.
Comment 1 Michael Pyne 2008-08-12 21:34:33 UTC
This has bit me as well before.

I think the "best" thing would be, if a shutdown were in progress, to save the bt somewhere and show it at next startup that such and such application crashed at last shutdown, that way there wouldn't be a dialog at all in that situation.
Comment 2 Pino Toscano 2008-10-26 15:27:50 UTC

*** This bug has been marked as a duplicate of bug 126073 ***