https://bugs.kde.org/show_bug.cgi?id=508366
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INTENTIONAL --- Comment #3 from Nate Graham <[email protected]> --- > I would prefer for it to be forced to close, or at least to have the option > to make that happen. You do have that option: use the "app not responding" window to force-close it. > If i've told an app to close, it is reasonable to > assume I dont want it to be open anymore. When an app is told to close but > doesnt, even if its just because it froze, it can be very disruptive to what > the user is doing. With a normal app this isn't too bad as you can just work > around it, but with games that are set to fullscreen it renders the entire > virtual desktop unusable until they close. They typically also make it so > the prompt does not show up properly so the user has to alt+tab to it first. This seems like something that's easy and obvious, but it's actually not. If we unconditionally force-closed windows that started hanging after some fixed period of time, it could cause data loss. Imagine the app starts hanging on close for 6 seconds to save its state. If an auto-kill timer killed it at 5 seconds, the app would die while it was still writing data to disk, and that data would be corrupted. With the app not responding window, you get to make the decision about whether the risk of this is acceptable to you, rather than the system making that decision for you. So I'm afraid we can't do what you're proposing, sorry. If you want to kill a hanging window right away, Meta+Ctrl+Esc will allow you to do that. -- You are receiving this mail because: You are watching all bug changes.
