Ubuntu
procps package

critical bug in top command package procps

  1. Trusty (14.04)
  2. Bug #1664535
Bug #1664535 reported by Pieter Steyn
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
procps (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Triaged
Undecided
Unassigned

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.

Revision history for this message
Pieter Steyn (pieterste) wrote :

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

Revision history for this message
Joshua Bayfield (jbayfield) wrote :

Hello,

Setting as confirmed - confirming that this occurs on Ubuntu Trusty (14.04) - process is killed even when Esc is used in top.

Changed in procps (Ubuntu):
status: New → Confirmed
Robie Basak (racb)
Changed in procps (Ubuntu Trusty):
status: New → Triaged
Changed in procps (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Robie Basak (racb) wrote :

17:18 <jbayfield> rbasak: Bug does not occur in Zesty/Yakkety.

17:18 <jbayfield> ie: it's already been resolved

17:18 <rbasak> Fix Released for the development release then. Thanks!

Revision history for this message
Pieter Steyn (pieterste) wrote :

Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.