https://bugs.kde.org/show_bug.cgi?id=500076
--- Comment #5 from cwo <cwo....@posteo.net> --- (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. -- You are receiving this mail because: You are watching all bug changes.
