This is not a bug in bash; it is acceptable for the receiving end of the
stdout pipe to be closed by grep once grep has found a match and exited.
It is a bug in the lsb-release command, which should not throw an
exception when stdout is closed.
Confirming this as a genuine bug, but declining it for Canonical to work
on as there is a straightforward workaround (redirecting stderr to
/dev/null to suppress the exception message).
** Package changed: bash (Ubuntu) => lsb (Ubuntu)
** Changed in: lsb (Ubuntu)
Importance: Undecided => Low
** Changed in: lsb (Ubuntu)
Status: Confirmed => Triaged
** Changed in: lsb (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
** Summary changed:
- grep -q gets broken pipe message with multiple expressions
+ lsb_release throws exception if stdout is closed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504127
Title:
lsb_release throws exception if stdout is closed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1504127/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
