Version: 2.2 (using 4.1.64 (KDE 4.1.64 (KDE 4.2 >= 20080828)), compiled sources) Compiler: gcc OS: Linux (x86_64) release 2.6.26-ARCH hello, as doing http://bugs.kde.org/show_bug.cgi?id=170432 I've noticed that after closing konsole powertop and iotop, which were ran inside konsole, were still running, both in a erroneous state, that is, using a lot of cpu. i had a similar problem with a program i develop, and it was solved with setpgrp (for bash process exec) and kill. maybe? bráulio
any news?
I presume the reason the child process is not being closed is because the parent process (Konsole) running as $USER doesn't have permission to kill the child which is running as root. > i had a similar problem with a program i develop, and it was solved with > setpgrp (for bash process exec) and kill. maybe? Can you expand on this?
uhm robert, you probably got the problem's reason. those process were really ran as root. but maybe the following method can fix this too. > Can you expand on this? after a fork() if you call setpgrp() the process is converted to a process group, so on a kill() call all its childs are killed too. you can also do it on qprocess' method: http://doc.trolltech.com/4.4/qprocess.html#setupChildProcess
Well, a bug report from 3 years ago :) I do not fully understand the mentioned problem(how was powertop/iotop run as root?). Anyway, I just committed some code for closing konsole session in a more reliable way, which may be also of help to this problem. If the reporter is still watching this report, could you please check this problem using the git version[1]? If it still happens, could you provide concrete and clear steps to reproduce it? [1] http://quickgit.kde.org/?p=konsole.git&a=summary
I would mark this as solved; I'm using konsole on a daily basis and never had this problem again. Thanks for the feedback!