43

When I want to shutdown my computer, I click shutdown, turn the screen off, and go to bed. Sometimes, I discover in the morning, that some applications crashed just after I clicked the shutdown button, and the report dialog prevented my computer from shutting down, which is just stupid.
Then, I propose that the crash report window auto-closes after some time, like one minute, because if something crashed while you're not in front of your computer, you don't really care, do you ?
The other solution would be to bypass the crash report when the computer is trying to shut down, but I think auto-closing the window is better.
What do you think ?

There is a use case which counters this.

Imagine I'm copying a file, walk away for a few minutes. Come back and find that dolphin is no longer open (for example).

I would really want to know that it has crashed.

Discuss.

david_edmundson wrote:There is a use case which counters this.

Imagine I'm copying a file, walk away for a few minutes. Come back and find that dolphin is no longer open (for example).

I would really want to know that it has crashed.

Solution: make sure the crash report doesn't block shutdown / stops blocking after a few minutes. So it only closes when a logout operation is being executed.

If your file copy operation crashed -> you see a crash report when you come back.
If something crashes when you shutdown -> report closed after a while (discussable)
You click shutdown while copying -> self-destruct! (maybe not)

what do you think?

david_edmundson wrote:Imagine I'm copying a file, walk away for a few minutes. Come back and find that dolphin is no longer open (for example).

I would really want to know that it has crashed.

Well, usually, when I copy a big file, I use to start the copy within dolphin, and then close it so that the copy keeps working in background. So, if I'm right, dolphin crashing would not stop your file copy.

But yes, maybe the good solution is to have nothing blocking after the shutdown has been initiated, so the modification would not be at the crash report level, but at the shutdown task level : any application should be killed after a timeout once it has been initiated. (Of course, that applies to disconnection and restart too)

cyberwan wrote:Well, usually, when I copy a big file, I use to start the copy within dolphin, and then close it so that the copy keeps working in background. So, if I'm right, dolphin crashing would not stop your file copy.

It does stop file copies. If you close dolphin normally, file transfer processes will continue. But if dolphin crashes, file transfer processes will hang. I posted a bug report about this a while back.

+1, but only on logout (or make autoclosing optional).

This seems like the wrong solution to the problem to my, I think your other suggestion is better:

The other solution would be to bypass the crash report when the computer is trying to shut down, but I think auto-closing the window is better.

There are situations when I don't want it to auto close. For example if something crashes when I'm away for a while, I want to know what happened to the application when I come back.

OK, it seems that the good thing to do is to shut down whatever happens after the request.

Should I change the idea title ?

I think this is still a valid idea, so you can post the second one (ignore crash dialog when shutting down) as a separate idea.

This is actually already reported at
https://bugs.kde.org/show_bug.cgi?id=126073
(also see the explanation at https://bugs.kde.org/show_bug.cgi?id=126073#c21)