bug 233994 might have the same cause as this one
--
unexpected behaviour of read in command_not_found_handle
https://bugs.launchpad.net/bugs/218748
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
Thank you for reporting back. Resetting status.
** Changed in: bash (Ubuntu)
Status: Incomplete => Triaged
--
unexpected behaviour of read in command_not_found_handle
https://bugs.launchpad.net/bugs/218748
You received this bug notification because you are a member of Ubuntu
Bugs, which
Same problem in Jaunty. I haven't installed Karmic yet.
--
unexpected behaviour of read in command_not_found_handle
https://bugs.launchpad.net/bugs/218748
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Confirmed on hardy. This should be reported upstream. I'll do it next
week if noone else beats me to it :)
** Changed in: bash (Ubuntu)
Importance: Undecided => Low
Status: New => Triaged
--
unexpected behaviour of read in command_not_found_handle
https://bugs.launchpad.net/bugs/218748
> Isn't this more of a bash(1) issue
Yes, it probably is. Sorry, I didn't think it through.
** Changed in: bash (Ubuntu)
Sourcepackagename: command-not-found => bash
--
unexpected behaviour of read in command_not_found_handle
https://bugs.launchpad.net/bugs/218748
You received this bug notificat
Isn't this more of a bash(1) issue that command-not-found?
--
unexpected behaviour of read in command_not_found_handle
https://bugs.launchpad.net/bugs/218748
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub