Hi again, I've done some digging and this is a known/fixed bug in procps version 3.3.10.
This is not backported to the latest 14.04.x in Ubuntu, and I believe it to be a severe enough bug to warrant such efforts. FYI: http://www.freelists.org/post/procps/top-Escape-doesnt-abort-kill- command,1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1664535 Title: critical bug in top command package procps Status in procps package in Ubuntu: New Bug description: I think I've discovered a bug in the linux top command. (Ubuntu 14.04 tested only) Steps to reproduce: $ top press k it then prompts for PID or selects top process by default press the esc key press esc key again Result: it kills the process anyway It's weird to me that the escape key is also seen as confirmation, though I should have probably used ctrl+c, it does not feel right. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1664535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
