command-not-found does not work when unknown command is piped to less/more
Bug #300647 reported by
Pavol Rusnak
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| command-not-found (Suse) |
Fix Released
|
Unknown
|
|||
| command-not-found (Ubuntu) |
Fix Released
|
Undecided
|
Michael Vogt | ||
Bug Description
Binary package hint: command-not-found
Steps to reproduce (can use more instead of less):
$ foobar | less
bash: foobar: command not found
lines ?-?/? (END)
[1]+ Stopped foobar | less
expected result:
$ foobar | less
bash: foobar: command not found
weirdly enough this works with cat, sed, tr and others
Revision history for this message
| Pavol Rusnak (prusnak) wrote | #1 |
| Changed in command-not-found: | |
| status: | Unknown → Fix Released |
Revision history for this message
| Michael Vogt (mvo) wrote | #2 |
| Changed in command-not-found (Ubuntu): | |
| assignee: | nobody → Michael Vogt (mvo) |
| status: | New → Fix Released |
To post a comment you must log in.
see https:/
there is a fix for this bug