Created attachment 178364 [details] "Close" button does nothing. I'm requesting that the Kill Dialog would spawn after a number of attempts of closing an app. In the attachment it shows a window that refuses to open, so using Alt+F4 and Ctrl+Meta+Esc doesn't work (I've tried clicking the skull on the icon on the panel and it killed plasma).
Or to better respect the user's autonomy, an option called "Terminate" could appear after trying to normally close the app a couple of times. If the user manages to press the "Close" button a couple of times, that means that the app is not responding.
Plasma already does this for applications that hang. What window did this happen with?
(In reply to cwo from comment #2) > Plasma already does this for applications that hang. What window did this > happen with? It was a Lutris (Flatpak) window.
(In reply to cwo from comment #2) > Plasma already does this for applications that hang. What window did this > happen with? I don't believe that the application was unresponsive as in frozen, I think it was unresponsive as in "I don't understand what the system is asking or/and I'm busy.". The solution presented in Comment 1 solves this issue because it uses the users themselves as timer by having them click "Close" too many times that it would be safe to assume the app is unresponsive in a unorthodox way.
(In reply to Fernando M. Muniz from comment #4) > I don't believe that the application was unresponsive as in frozen, I think > it was unresponsive as in "I don't understand what the system is asking > or/and I'm busy.". "I'm busy" should count as unresponsive. > The solution presented in Comment 1 solves this issue because it uses the > users themselves as timer by having them click "Close" too many times that > it would be safe to assume the app is unresponsive in a unorthodox way. I am a bit concerned here; if the app is still resposive it might be because it is in a state where killing it could lead to data corruption or loss. Simplest case is that it popped up a "you have unsaved changes" dialog that did not get raised for some reason, or it is in the process of saving a very large file that would get corrupted if interrupted. Offering to force close seems dangerous here (and is always available from the system monitor). In this particular case it seems like there was another issue with the window in that it seemed like it couldn't be activated, which to me seems like the real bug. (Or that it somehow did not register as unresponsive). But I'll let someone else handle this.
Many, many everyday users furiously repeat clicks (I've personally seen 3-4 per second) on interface elements that don't instantly respond. This proposal would cause Plasma to suggest to such folks that they perform an action that would likely lead to data loss, including in cases where a program is just taking a few seconds "cleaning up". In the situation shown in that video, Meta+Esc to pull up System Monitor, then selecting the problematic application and choosing Quit (or the equivalent on the Processes tab) would have solved the issue. I'm happy to be overridden by a developer here if appropriate, but I believe System Monitor would be the intended workflow in this situation.
In this case I think Fernando is requesting it only when repeatedly trying to close an app — e.g. by clicking the window close button or closing the app using Alt+F4, not just when repeatedly clicking any UI element. I agree that doing it for any UI element would be highly dangerous. The problem here is that the hanging app was Lutris, which uses CSDs, which means the close button was drawn by the app rather than KWin, which means the close button was probably non-functional too, and there was no way for KWin to detect that. Perils of using CSD apps. However KWin could probably detect repeated presses of Alt+F4.