Red Hat Bugzilla – Bug 69221
child application terminated when console is killed.
Last modified: 2007-04-18 12:44:17 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux)
Description of problem:
When an application, say xemacs, is launched from within a konsole or an xterm, that
application is terminated when the user terminates the konsole or xterm by clicking on the
close window button. The application is NOT terminated when the user types 'exit' from within
the konsole/xterm that was used to launch the application.
This behavior exists in both the kde version supplied by redhat as well as a kde 3.0.2 I built on
limbo. Although, the latter has some more unpleasant consequences, i.e., if the user
launches konqueror from a konsole, kills the konsole by clicking the close window button,
again, both konsole and konqueror terminate, but now a mutex is not released and the user can
no longer run (at least) konqueror, kspread, and kword.
Hopefully, the user saved their work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. launch konsole or xterm
2. enter the following command 'xemacs &'
3. kill the konsole by clicking the 'close' window button.
4. that konsole and emacs will both terminate
Expected Results: the konsole should terminate. my xemacs session should not.
hmm, normal behaviour, if a shell gets a SIGHUP... though konsole should warn
about running apps...
This is not normal behaviour in Red Hat 7.3. Further, this does not happen in limbo if you su - to
another user, then launch the application, and then kill the console.
Oops, I guess this is normal shell behaviour with bash. tcsh behaves
differently. Sorry. Not a bug?