https://bugs.kde.org/show_bug.cgi?id=454751
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |INTENTIONAL CC| |[email protected] --- Comment #3 from TraceyC <[email protected]> --- Since there have been no other feature requests or bug reports about this that I can find, I'm going to close this back out. Simply, if a user finds out by accident that sending SIGSTOP will cause System Monitor to freeze, because they sent it a command that says "Suspend (STOP)", they will see that suspend does what it says. Eventually, if you try to right click and close the window, you will get the "Not Responding" dialog that allows an easy way to kill the suspended window. To be fair, there is a request in bug 444666 for tooltips for End Process and Send Signal. Those would make it more clear to a curious user what they're about to do. which would mitigate this. -- You are receiving this mail because: You are watching all bug changes.
