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

[Bill Zaumen]

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
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