I just ran into this bug and there seems to be a path-name dependency on it showing up. In some directories it happens consistently, making it a real annoyance. If it is in fact dependent on the length of a pathname, or the form of a directory name, that might be useful in locating the cause.
Here are the commands I used (my home directory is /home/wtz ): cd ~ mkdir -p Projects cd Projects mkdir Foo cd Foo mkdir Test cd Test mkdir org cd org mkdir bzdev cd bzdev mkdir ejws foo & [crashes? - may be intermittent ] cd ~/Projects cd Foo cd Test/org/bzdev foo & [error message ending with foo: command not found] cd ~ cd Projects cd Foo cp -r Test Test-Test cd Test-Test/org/bzdev foo & [gnome terminal disappears] It acts like having the '-' in the directory name is related to the problem, but it could just be the path-name length, directory-name length, etc. In a subdirectory of a directory that has a '-' in the file name, the bug seems to always occur. I'm using a fairly recent version of Ubuntu (10.10) on a 2-core, Intel i3 with two threads per core. Also, it seemed there was a dependency on whether the directory the command was run with had files or subdirectories in it (which needs to be verified, of course). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/241331 Title: Running a non-existing command in the background causes exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/241331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
