Bug 440499

Summary:	Plasma System Monitor does not list Dolphin launched by global shortcut
Product:	[Applications] plasma-systemmonitor	Reporter:	Ilya Bizyaev <bizyaev>
Component:	general	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	ahiemstra, jodr666, kde, kde, nate, plasma-bugs
Priority:	NOR
Version:	5.22.4
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Demo

Description Ilya Bizyaev 2021-08-01 14:33:24 UTC

SUMMARY
If I launch Dolphin from Kickoff, the new System Monitor displays it, but if I instead use the global shortcut (Meta+E), it is not listed.


STEPS TO REPRODUCE
1. Launch plasma-systemmonitor
2. Use Meta+E to launch Dolphin

OBSERVED RESULT
Dolphin is not listed as a running application.


EXPECTED RESULT
Dolphin is always listed when running.


SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.3
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
Graphics Platform: X11

Comment 1 Tony 2021-08-02 00:48:47 UTC

Created attachment 140457 [details]
Demo

Can confirm this one.
It does not get registered when meta+e is used to launch it as shown at the end in the attacth demo.
It happens with systemdBoot on and off.

Comment 2 Arjen Hiemstra 2021-08-02 13:13:32 UTC

Hmm, this is caused by whatever launches Dolphin when the shortcut is pressed not using the right APIs for that, which means that rather than Dolphin being launched in its own CGroup, it becomes a child of the launcher process. Since this is most likely some service that we don't show in the Applications table, Dolphin doesn't show up.

Can you share the output of systemd-cgls so I can confirm?

Comment 3 Nate Graham 2021-08-02 18:45:23 UTC

Can also confirm. Here is the relevant output of systemd-cgls:

│   │ │ ├─app-org.kde.konsole-9123ceda2c4643438e50ecaa640218a1.scope 
│   │ │ │ ├─133864 ksystemstats --replace
│   │ │ │ ├─133865 kded5 --replace
│   │ │ │ ├─133867 /bin/bash
│   │ │ │ ├─133874 kglobalaccel5
│   │ │ │ ├─133876 kdeinit5: Running...
│   │ │ │ ├─133893 /home/nate/kde/usr/lib64/libexec/kf5/klauncher --fd=8
│   │ │ │ ├─133969 /home/nate/kde/usr/lib64/libexec/kf5/kioslave5 /home/nate/kde/usr/lib64/plugins/>
│   │ │ │ ├─133971 /home/nate/kde/usr/lib64/libexec/kf5/kioslave5 /home/nate/kde/usr/lib64/plugins/>
│   │ │ │ ├─134351 /home/nate/kde/usr/lib64/libexec/kf5/kioslave5 /home/nate/kde/usr/lib64/plugins/>
│   │ │ │ ├─134353 /home/nate/kde/usr/lib64/libexec/kf5/kioslave5 /home/nate/kde/usr/lib64/plugins/>
│   │ │ │ ├─144969 dolphin [kdeinit5]
│   │ │ │ ├─144997 /home/nate/kde/usr/lib64/libexec/kf5/kioslave5 /home/nate/kde/usr/lib64/plugins/>
│   │ │ │ ├─144999 /home/nate/kde/usr/lib64/libexec/kf5/kioslave5 /home/nate/kde/usr/lib64/plugins/>
│   │ │ │ ├─145001 /home/nate/kde/usr/lib64/libexec/kf5/kioslave5 /home/nate/kde/usr/lib64/plugins/>
│   │ │ │ ├─145004 /home/nate/kde/usr/lib64/libexec/kf5/kioslave5 /home/nate/kde/usr/lib64/plugins/>
│   │ │ │ ├─145007 /home/nate/kde/usr/lib64/libexec/kf5/kioslave5 /home/nate/kde/usr/lib64/plugins/>
│   │ │ │ └─145009 /home/nate/kde/usr/lib64/libexec/kf5/kioslave5 /home/nate/kde/usr/lib64/plugins/>


This may be slightly different from other people's output since I launched stuff from terminal commands due to running in a git master session. Nonetheness, it does seem odd that dolphin's parent process is listed as konsole.

Comment 4 David Edmundson 2021-08-05 14:13:53 UTC

This is dependent on whether klauncher5 is running.

kglobalaccel code uses klauncher5 first if it's available before doing the "right" path.

To some extent this will go away when we make KDE_FORK_SLAVES as default and then kill anyone doing things with klauncher

Comment 5 David Redondo 2021-08-30 13:48:55 UTC


*** This bug has been marked as a duplicate of bug 433362 ***