Ubuntu
procps package

/bin/kill no longer works with negative PID

Bug #1077796 reported by Michael Selig
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
procps (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Incorrectly gives a usage message, eg:

/bin/kill -1 -4321
==>
/bin/kill: invalid option -- '4'

A workaround appears to be to use "--" before the PID, but this is unsatisfactory, as existing scripts would have to be modified when they shouldn't have to be.

This problem has only appeared recently in 12.10.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in coreutils (Ubuntu):
status: New → Confirmed
Revision history for this message
C de-Avillez (hggdh2) wrote :

Thank you for this bug and helping making Ubuntu better.

Please run '/bin/kill --version', and report back the version. Also, next time please use 'ubuntu-bug' to open a bug. For example, in this case, 'ubuntu-bug coreutils'.

Changed in coreutils (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Michael Selig (michael-selig) wrote :

/bin/kill --version
==>
kill from procps-ng 3.3.3

This is from Ubuntu 13.04. When I reported the bug originally it was on 12.10 (which I no longer use). However the bug is still there on 13.04, unfortunately.

PS: Why has it taken over 8 months for this bug to be acknowledged? I thought it must have vanished into the bug black hole.

Revision history for this message
Riku Voipio (riku-voipio) wrote :

This should be reassigned to procps, /bin/kill is not in coreutils.

In debian this has been fixed procps-ng 3.3.4.

Revision history for this message
C de-Avillez (hggdh2) wrote :

Indeed, done. Bug marked Triaged.

@Michael Selig: one of the reasons it took that long is that there are very few volunteers to work on the bugs.

affects: coreutils (Ubuntu) → procps (Ubuntu)
Changed in procps (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Trent Lloyd (lathiat) wrote (last edit ):

Most shells (including bash, zsh) have a built-in for kill so it's done internally. Some shells don't so it executes /bin/kill instead which has this issue.

One comment noted this was fixed at some point in 2013 in version 3.3.4 but it apparently broke again at some point and is broken at least in 20.04 Focal's v3.3.16.

This was recently fixed again upstream here:
https://gitlab.com/procps-ng/procps/-/merge_requests/77

Upstream v3.3.16 (in 20.04 Focal and 20.10 Hirsute) was released Dec 2019 without this fix. That fix was submitted upstream 3 years ago but only merged 11 months ago and was included in the v3.3.17 release which was made in Feb 2021 so not included in 20.04 Focal. 3.3.17 with the fix is already in 21.10 Impish.

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.