This bug was fixed in the package bash - 5.0-6ubuntu2

bash (5.0-6ubuntu2) groovy; urgency=medium

  * Apply upstream patches 017 (LP: #1878517)

 -- Matthieu Clemenceau <>  Thu, 18 Jun
2020 10:44:55 -0500

** Changed in: bash (Ubuntu)
       Status: In Progress => Fix Released

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.

  please apply bash 5.0 patch 17

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Focal:

Bug description:
  I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0
  patch 16.

  I can't reproduce it in pure bash, but with bats from it is very easy to repro:

  # cat << EOF > ya.bats
  check() {
        echo "check $@"
        ls -l /proc/self/fd

  @test "here file" {
        check -p <(echo "hey")

  $ bats ya.bats

  Normally the output should contain the line

     lr-x------ 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]

  which is a result of a "here file" created by bash via <(echo "hey").

  In my testing, about 50% of runs don't have /dev/fd/63 listed.

  I found out this is a manifest of a bug introduced in bash 5.0 patch
  16 (see

  The bug is fixed in 5.0 patch 17 (see

  Please update bash to patchlevel 17.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to