Comment 12 for bug 127399

I can confirm that this bug still exists in karmic.

Here's how I can reproduce it 80% of the time:
=====================================================
helmert@alfons:~$ bash && echo bash is done
helmert@alfons:~$ cd tmp/
helmert@alfons:~/tmp$ rubbish &
[1] 26946
helmert@alfons:~/tmp$ exit
bash is done
=====================================================

Note that I don't type the "exit" -- it appears automatically. bash decides to exit after I try to invoke a nonexistent command ("rubbish" above) in the background. Interestingly, the problem only occurs for me if I'm *not* in my home dir, hence the cd at the start. (No idea what this has to do with anything.)

I'm not a bash expert, but to me this looks like there might be some sort of race condition between the command-not-found-handler and the background process (PID 26946 above) at the core of this.