[Konsole-devel] [Bug 176963] New: when started through kde, all konsole instances share the same PID. Killing one kills all.

[as at shehata.com]

http://bugs.kde.org/show_bug.cgi?id=176963

           Summary: when started through kde, all konsole instances share
                    the same PID. Killing one kills all.
           Product: konsole
           Version: unspecified
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: konsole-devel at kde.org
        ReportedBy: as at shehata.com


Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

If I start multiple konsoles using the menu or F2 they all inherit the same
PID. As I've read in 161248, this seems to be intentional!?

This has pretty bad side effects though imho. 

If you start multiple konsoles on multiple desktops, and some of the konsoles
hang because of some app in the terminal dying for some reason (remote ssh
closed or crashed - whatever) then this konsole becomes useless. After a few
days you have a large number of useless konsoles - but alas, they can't be
killed. If I use xkill on one of them, ALL konsoles die, since they all run
under the same PID!

As I see it it's just the way KDE starts the konsole. If there's already a
konsole process, it attaches to that. If I start "konsole" from an xterm or
another konsole, everything's good, each gets its own process.
But the problem is again there when you have a tab hang, and you want to detach
it and kill it. Again, this will kill the parent konsole.
I know that this worked fine in KDE 3, both with starting multiple instances
from the GUI, and with detached tabs. I think wasting a few MBs is well worth
it in this case, at least there could be an option...

Thanks!


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.