Does running the script mentioned above with bash (as opposed to plain sh) explicitly affects the problem?
Could you change #!/bin/sh to #!/bin/bash and try again? -- command-not-found weird behavior in bash https://bugs.launchpad.net/bugs/103331 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
