I had a look at the bash code that handles this, but there's so much conditional forking and all... really way over my head for now.
As a guidance for setting the importance of this bug (to whomever is allowed to do that), I'd say it is of low importance. I just played around a bit in gdb, and the shell will refuse to exit when there are stopped jobs, so you won't lose work to this bug (as mentioned in my previous comment: you even keep your command history). Attached is the console output of that playing around. ** Attachment added: "241331stoppedjobs.txt" http://launchpadlibrarian.net/22538071/241331stoppedjobs.txt -- Running a non-existing command in the background causes exit https://bugs.launchpad.net/bugs/241331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
