Created attachment 111282 [details] Konsole info from ksysguard So... I have no idea what this is. So let me put it like this: I am working in terminals from time to time obviously, but sometime I notice my fans starting spinning quite loudly and then I check ksysguard and is always a goddamn konsole process eating 12-13% of the CPU. I am not sure why this is. It seems that it is always a konsole instance related to something I was just doing, for example right now I was working in vim so I got yet another phantom konsole appearing. After some digging I can say this: I have no actual konsole opened myself, but I closed one recently krunner has it's run commands option stopped this konsole processes are made by kinit5 I will provide attachments with the info I managed to get. P.S. I tried asking a friend and reddit but no help.
Created attachment 111283 [details] systemctl status
Created attachment 111284 [details] ksysguard picture
So I was just working in yakuake in a folder called test on the desktop. Now I yet again got a phantom konsole appearing. 7536 konsole [kdeinit5] --workdir /home/raitaro/Desktop/Tes
I have found the problem. If I open vim, type something then close the window suddenly the konsole does not close. This seems to be a lattedock issue, so I will open an issue there to see where this is going.
Created attachment 111315 [details] Bug report
https://github.com/psifidotos/Latte-Dock/issues/920
Latte is not the issue actually. Even if I open a file in vim using open with I can still have the konsole not properly close itself.
I can't reproduce this, I've run grep via watch in a gnome-terminal to watch and the konsole instance disappears immediately. Can you please retest and confirm if this is still an issue, thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!