Bug 488022

Summary: Multiple instances of gkrellm upon reboot or logout/login
Product: [Plasma] plasmashell Reporter: S. Umar <sait.a.umar>
Component: Session ManagementAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: kde, natalie_clarius
Priority: NOR    
Version First Reported In: 6.0.5   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description S. Umar 2024-06-04 15:03:22 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY

I have gtk app gkrellm on my desktop. I just noticed that everytime I login/logout OR even after every reboot there is an extra session of gkrellm running. It just keeps growing. I have done a killall -HUP gkrelmm and tested again multiple times with the same result. Eventually they start consuming significant amount of CPU.
PS: I am running plasma-X11. I have not tested with Wayland.


STEPS TO REPRODUCE
1.  start gkrellm on desktop
2. login/logout or reboot
3. ps -e |grep gkrellm

OBSERVED RESULT
multiple instances of gkrellm upon reboot or login/logout

EXPECTED RESULT
Single instance of gkrellm

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0 (some 6.2.1 and 6.2.2)
Qt Version: 6.7.1

ADDITIONAL INFORMATION
Comment 1 David Redondo 2024-06-05 07:45:02 UTC
Is that app maybe autostarted?
Comment 2 S. Umar 2024-06-05 12:12:38 UTC
No, it is not. There is nothing in .config/autostart. Is there another place for autostart? I see it in .config/ksmserverrc as:
--------------------
[LegacySession: saved at previous logout]
clientMachine1=localhost
clientMachine2=localhost
command1=gkrellm
command2=gkrellm
count=2
----------------------
I also see multiple instances I (after logging in and out) in kwin_saved\ at\ previous\ logout_
resourceClass1=Gkrellm
resourceClass2=Gkrellm
resourceClass3=plasmashell
resourceClass4=Gkrellm
resourceClass5=gkrellm
resourceClass6=plasmashell
resourceName1=gkrellm
resourceName2=gkrellm
resourceName3=plasmashell
resourceName4=gkrellm
resourceName5=gkrellm
resourceName6=plasmashell

......


wmCommand1=gkrellm\s
wmCommand2=gkrellm\s
wmCommand3=
wmCommand4=gkrellm\s
wmCommand5=gkrellm\s
wmCommand6=
Comment 3 S. Umar 2024-06-05 12:14:38 UTC
Also in, .local/share/plasmasessionrestore/plasmasessionrestorestaterc 

[0]
appId=gnome-gkrellm.desktop

[1]
appId=gnome-gkrellm.desktop
Comment 4 S. Umar 2024-06-05 17:29:37 UTC
The logout works with Plasma Wayland. The problem  seems to be with Plasma(X1). However, I can't use Wayland because some apps are very jittery, like chrome and linreoffice.
Comment 5 David Redondo 2024-06-14 08:15:13 UTC
Does every log in add a new instance of  .config/ksmserverrc ?

If you close the instances, does the process maybe keep running?
Comment 6 S. Umar 2024-06-14 16:48:17 UTC
Actually the files in comment #2 were the problen. I went ahead and edited them, removing all the extra accurances of gkrellm  and plasmashell and just leaving one instance. After that it stopped adding additional instances, I think what happened is that every time I got a new workstations I copied my old home directory to the new one, which may have created multiple instances after new login. In any case I fixed it on all my computers. I think we can close this case.
Comment 7 Bug Janitor Service 2024-06-29 03:47:29 UTC
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!
Comment 8 S. Umar 2024-06-29 11:48:09 UTC
per comment #6 the issue is resolved.