[Bug 241331] Re: Running a non-existing command in the background causes exit

[Richard G. Clegg]

Good catch.  I confirm that path length does seem to be an issue here.
This bug has been around since 2008 now -- it's very annoying.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/241331

Title:
  Running a non-existing command in the background causes exit

Status in “bash” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-terminal

  In Ubuntu 8.04, running a command which does not exist can sometimes
  cause an exit command.  Here is an example cut and pasted when gnome-
  terminal is set to "stay open on exit".

  richard at sepulchrave:~$ gedit test &
  [1] 13336
  richard at sepulchrave:~$ gdit test &
  [2] 13340
  richard at sepulchrave:~$ exit

  Other times  the exit will not happen but the command will return an
  Exit 127 status.

  richard at sepulchrave:~$ gdit test &
  [1] 13403
  richard at sepulchrave:~$ bash: gdit: command not found

  [1]+  Exit 127                gdit test
  richard at sepulchrave:~$ gdit test &
  [1] 13405
  richard at sepulchrave:~$ exit

  Package is
  gnome-terminal:
    Installed: 2.22.1-0ubuntu2
    Candidate: 2.22.1-0ubuntu2
    Version table:
   *** 2.22.1-0ubuntu2 0
          500 http://gb.archive.ubuntu.com hardy/main Packages
          100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/241331/+subscriptions