Description of problem: %subj% Version-Release number of selected component (if applicable): kdebase-4.0.5-5.fc9.x86_64 How reproducible: every time Steps to Reproduce: 1. $ konsole 2. $ sudo -i 3. # top 4. *close* konsole by using X at top right Actual results: $ ps xua | grep top you'll see top running Expected results: killed top, or whatsoever was ran in sudo
doubt there's anything to do to fix that. ?? See, top is now running as root, and your user permissions aren't enough to terminate it anymore.
It *may* be possible, but only if sudo can act as a proxy to forward signals (which I doubt)
I believe it is odd behaviour ... everything must be killed inside. can you reproduce the problem?
I can reproduce it alright, I'm just saying what you want/expect may not be possible.
Indeed. And in any case, this is not a bug in Konsole, in fact it has nothing to do with Konsole at all.
(In reply to comment #4) Okay,... Why does this work as I'm expecting in gnome-terminal then?
gnome-terminal does the same as konsole for me. I see top processes (owned by root) still running after close.
I would like to close kernel issues in the same way... >:) It _is_ the problem, not the problem of konsole, may be but the problem of kde, may be kwin, I do not know... I just tried to see what the KDE4 _is_... Just try to do the same in gnome environment in any terminal(not sure about konsole). It kills everything inside the terminal, no matter in sudo or not. It works just fine in WMII as well. The only WM/DE so far that did not kill apps inside sudo is KWIN/KDE. I want it fixed from the moment when the report was marked as NOTABUG! =)
To be clear and re-iterate. I can't reproduce this. gnome-terminal for me does the same thing as konsole.
Did you try to reproduce it in another WM/DE ?
had a chance to test in kde3. works fine == everything was killed inside the terminal.
We found that this bug has been already registered in the upstream database (https://bugs.kde.org/show_bug.cgi?id=143880) and believe that it is more appropriate to let it be resolved upstream. We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report.