[Bug 298480] Re: Konsole should not terminate background processes upon closing konsole window

Thu Sep 5 10:46:09 UTC 2013

Launchpad has imported 9 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=185140.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2009-02-21T17:14:53+00:00 Johnathon wrote:

Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    I Don't Know

Originally posted on Launchpad:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/298480

Summary:
Konsole should not close background apps (processes called by "command &") upon closing konsole window.

To reproduce:
Open console
Type in kate &
Close konsole window
Kate window also closes

Currently, gnome-terminal supports this feature.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/298480/comments/5

------------------------------------------------------------------------
On 2009-03-10T20:15:08+00:00 Matthew Woehlke wrote:

...then gnome-terminal is broken. Allowing jobs to run after the parent
dies is creating orphans. (Whether gnome-terminal fails to shut down the
shell in this case, or has a misfeature to detect still-running jobs and
disown them, neither is a good idea.) To understand why this is bad,
consider if the child process is a CLI program that needs an associated
tty; you now have a child running that is useless but can't be stopped
except by searching the system process list for it and using 'kill'.
Neither the shell nor the terminal emulator should be second-guessing
the user this way.

Fortunately, there are already ways to indicate that you wish a child
process to ignore termination of the parent. The canonical way is
'nohup'. In bash, it's often easier to 'disown' such children
(especially if you forgot to use 'nohup' to start the child), i.e. 'kate
& disown'.

(Having said that, it would be nice if konsole would integrate
detachable sessions, mainly so that crashes wouldn't take out all my
shell sessions, but that's a different issue.)

@Robert: I'm closing this WONTFIX. Obviously as the maintainer you can
decide that's wrong :-), but IMO "fixing" the "bug" exactly as written
would be broken.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/298480/comments/6

------------------------------------------------------------------------
On 2009-03-10T23:08:16+00:00 Robert Knight wrote:

No, I agree with the reporter about what I expect to happen - and it
does for me.  If I start a Konsole session, run kate& and quit the
session and also Konsole then Kate stays running as I expect.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/298480/comments/7

------------------------------------------------------------------------
On 2009-03-10T23:09:10+00:00 Robert Knight wrote:

Also, about accidentally exiting with running jobs - the shell will,
depending on its current settings, warn you about that.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/298480/comments/8

------------------------------------------------------------------------
On 2009-03-10T23:12:18+00:00 Robert Knight wrote:

I was able to reproduce.  Normally I close tabs by pressing Ctrl+D to
tell the shell to exit - in this case, kate stays running in the
'background'.  If on the other hang I put kate in the background and
close Konsole via File -> Close Window then Kate exits.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/298480/comments/9

------------------------------------------------------------------------
On 2009-03-12T00:07:20+00:00 Matthew Woehlke wrote:

Right, I had no trouble reproducing, but I don't see how you can fix it
other than to either a: not sighup bash, or b: rely on detecting bash
complaining about stopped jobs, or...

Eew. I tried your way; apparently on EOF, bash happily disowns anything
in the background without warning? That feels icky.

Ah, well, I guess the solution then is that Konsole should always try to
kill shells with EOF before resorting to SIGHUP. I'm still not sure how
I feel about that, though; what if I am running a process where EOF will
cause something to happen that I don't want, but SIGHUP would be fine?

(Meanwhile, I have asked Chet if this is desired behavior. Alas, I would
have to install another shell to check if this is typical.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/298480/comments/10

------------------------------------------------------------------------
On 2009-03-12T23:06:10+00:00 Matthew Woehlke wrote:

Hmm... well, I still don't really like this behavior, but Chet has
spoken: http://permalink.gmane.org/gmane.comp.shells.bash.bugs/12602.

So according to him, Konsole should send EOF when anything (tab or whole
app) is closed "nicely".

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/298480/comments/11

------------------------------------------------------------------------
On 2009-06-26T18:20:40+00:00 Matthew Woehlke wrote:

*** Bug 197875 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/298480/comments/12

------------------------------------------------------------------------
On 2011-10-24T14:28:58+00:00 adaptee wrote:

(In reply to comment #6)

The unfortunate fact is currently most emulators do not. From my
observation, xterm/vte/uxvt-unicode/mlterm all send SIGHUP thus killing
background processes, while putty is the only one which sends EOF.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/298480/comments/14

** Changed in: kde-baseapps
       Status: Confirmed => Unknown

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

Title:
  Konsole should not terminate background processes upon closing konsole
  window

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/298480/+subscriptions