[opensuse] why does konsole use processor power after it's closed?
Hi, I'm here on leap 42.1 with kde 5. Sometimes I use konsole to do some little things, then I close it. But it seems the program does not terminate. Right now I had two Konsole processes, each consuming 13% of my i7 cpu power - but no konsole window open and nothing that could still run within konsole. I am sure that there is nothing running, because I just used it to start a program, terminated it and was back on the prompt again before I exited konsole. I then kill these processes manually. Of course I can do that whenever I use konsole, but shouldn’t a program terminate itself when its terminated and stop eating my battery? And what could konsole do that uses 13% of such a powerful processor? Anybody else sees this problem? What could I do? Daniel -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 15.08.2016 um 00:37 schrieb Carlos E. R.:
On 2016-08-14 19:40, Daniel Bauer wrote:
Anybody else sees this problem? What could I do?
You could attach a trace to the PID of the process and find out :-?
I tried (once as user, once as root): strace -e trace=open -p 3252 -o /home/daniel/Desktop/konsoleout.txt let it run some minutes but there was only a empty file produced. (I also tried with adding "-s 80") this is output of top: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3252 daniel 20 0 419472 56124 40984 R 93.75 0.354 12:40.37 konsole When I open a konsole a new process is created, it has 0% cpu and 15820 K memory. When I close that konsole window (without having entered anything on the prompt), the cpu goes to 13% (alters between 12 and 13%) in kde's ctrl-esc. It /seems/ that if I enter "exit" (instead of simply closing the window) the process gets terminated, it disappears. As much as I remember the bash had to be exited explicitly with the exit-command in very early versions (SuSe 6.x), but since years and until 13.2 the close-window-click fully exited konsole. Has this changed back to old behavior or is there somewhere a setting that delivers the exit command to konsole when clicking the close window button? -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Daniel Bauer wrote:
Am 15.08.2016 um 00:37 schrieb Carlos E. R.:
On 2016-08-14 19:40, Daniel Bauer wrote:
Anybody else sees this problem? What could I do?
You could attach a trace to the PID of the process and find out :-?
I tried (once as user, once as root):
strace -e trace=open -p 3252 -o /home/daniel/Desktop/konsoleout.txt
let it run some minutes but there was only a empty file produced. (I also tried with adding "-s 80")
Maybe try it without "-e trace=open" - strace -p 3252 That ought to show you what's going on. -- Per Jessen, Zürich (20.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 15.08.2016 um 09:34 schrieb Per Jessen:
Daniel Bauer wrote:
Am 15.08.2016 um 00:37 schrieb Carlos E. R.:
On 2016-08-14 19:40, Daniel Bauer wrote:
Anybody else sees this problem? What could I do?
You could attach a trace to the PID of the process and find out :-?
I tried (once as user, once as root):
strace -e trace=open -p 3252 -o /home/daniel/Desktop/konsoleout.txt
let it run some minutes but there was only a empty file produced. (I also tried with adding "-s 80")
Maybe try it without "-e trace=open" -
strace -p 3252
That ought to show you what's going on.
tried, gave also empty file. to be sure that I looked at the right file, I killed the process from kde-ctrl-esc and the only content I received in the trace file is this: --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=4993, si_uid=1000} --- +++ killed by SIGTERM +++ So it uses 13% CPU but does nothing :-( -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Daniel Bauer wrote:
Am 15.08.2016 um 09:34 schrieb Per Jessen:
Daniel Bauer wrote:
Am 15.08.2016 um 00:37 schrieb Carlos E. R.:
On 2016-08-14 19:40, Daniel Bauer wrote:
Anybody else sees this problem? What could I do?
You could attach a trace to the PID of the process and find out :-?
I tried (once as user, once as root):
strace -e trace=open -p 3252 -o /home/daniel/Desktop/konsoleout.txt
let it run some minutes but there was only a empty file produced. (I also tried with adding "-s 80")
Maybe try it without "-e trace=open" -
strace -p 3252
That ought to show you what's going on.
tried, gave also empty file. to be sure that I looked at the right file, I killed the process from kde-ctrl-esc and the only content I received in the trace file is this:
--- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=4993, si_uid=1000} --- +++ killed by SIGTERM +++
So it uses 13% CPU but does nothing :-(
It's clearly not just looping, but it is odd that it doens't do any system calls. -- Per Jessen, Zürich (20.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/15/2016 03:31 AM, Daniel Bauer wrote:
It /seems/ that if I enter "exit" (instead of simply closing the window) the process gets terminated, it disappears.
As much as I remember the bash had to be exited explicitly with the exit-command in very early versions (SuSe 6.x), but since years and until 13.2 the close-window-click fully exited konsole.
Has this changed back to old behavior or is there somewhere a setting that delivers the exit command to konsole when clicking the close window button?
Well I think that is the real issue; forget all this tracing, you've easily determined the underlying cause of the excess CPU burning. Your question about the regression is a perfectly valid one and it the one that this thread SHOULD be addressing, not how to run a trace. Of course the existence of a 'rougue' shell 'should/ show up with 'ps'. Incidentally, what kernel, version of KDE and of konsole are you running? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I just found the bug https://bugs.kde.org/show_bug.cgi?id=343803 when I wanted to report it... at least I am not the only one... I can confirm that it has to do with Nvidia. When I change to intel graphics, konsole behaves and closes normal. When I change back to nvidia the problem is here again. So, until a new Nvidia driver is in the official updates, I'll go back to earlier days and close the window with typing exit. Maybe this step back makes me younger, too :-) gave a great day! Daniel Am 14.08.2016 um 19:40 schrieb Daniel Bauer:
Hi,
I'm here on leap 42.1 with kde 5.
Sometimes I use konsole to do some little things, then I close it. But it seems the program does not terminate. Right now I had two Konsole processes, each consuming 13% of my i7 cpu power - but no konsole window open and nothing that could still run within konsole.
I am sure that there is nothing running, because I just used it to start a program, terminated it and was back on the prompt again before I exited konsole.
I then kill these processes manually.
Of course I can do that whenever I use konsole, but shouldn’t a program terminate itself when its terminated and stop eating my battery? And what could konsole do that uses 13% of such a powerful processor?
Anybody else sees this problem? What could I do?
Daniel
-- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-08-15 11:49, Daniel Bauer wrote:
I just found the bug https://bugs.kde.org/show_bug.cgi?id=343803 when I wanted to report it... at least I am not the only one...
See #41 and #64 The issue is considered solved by them, it seems, with some version of nvidia driver - except for some machines that can not update to it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (4)
-
Anton Aylward -
Carlos E. R. -
Daniel Bauer -
Per Jessen