Comment #1 is correct. This is the intended behaviour of the system.
When you start a process it is always as a child of another, usually
some session. Graphically, you log in to a desktop session. When you
start gnome-terminal you are beginning a separate shell session and any
programs started in that terminal belong to the shell session [1].
There are good reasons for this design.
Any program can be started in the desktop session, without needing a
menu entry. For example, GNOME provides the run program dialog (ALT-F2)
for this purpose. If you desire a program to last for the duration of
the desktop session, start it using the run dialog and *not* from gnome-
terminal.
[1] Some programs apparently take measures to escape from the shell
session so that they appear to run in the desktop-session. These are
exceptional and should not be considered the norm. If you start a
program from a shell session you should expect that it will remain under
the control of that shell.
** Changed in: gnome-terminal (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/819842
Title:
Commands in the background are terminated after closing the terminal
Status in “gnome-terminal” package in Ubuntu:
Invalid
Bug description:
I'm using Ubuntu 11.10 dev and if I open an application in the
terminal (for example "git gui &" and "scite &") I get the output "[1]
12619" (dependend on the job and pid) and can continue using the
terminal. The problem is if I close the terminal the application is
terminated too. I tested this with gnome-terminal 3.0.1-0ubuntu3 and
lxterminal 0.1.11-0ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/819842/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
