Bug 441628

Summary:	Apps launched via global shortcut do not seem to be getting put in their own cgroup
Product:	[Frameworks and Libraries] frameworks-kglobalaccel	Reporter:	hsnnsnc <hasannisanci>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	ahiemstra, kde, kde, nate, plasma-bugs
Priority:	NOR
Version:	5.85.0
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:

Description hsnnsnc 2021-08-27 20:37:27 UTC

SUMMARY

In KDE Plasma, when you run an application (eg: Dolphin) with a shortcut (Meta+E), it is not listed in "System Monitor" - "Overview" - "Application". But the same application: If you open it in Panel, Menu or ".desktop" file on Desktop, it will be listed under "System Monitor" - "Overview" - "Application".

This applies to Autostart. So if you set an application to start automatically when KDE Plasma is started, the application you want to start automatically is not listed under "System Monitor" - "Overview" - "Application".

I think this situation is not normal.

A little note: This also applies when you start with "Konsole".


OBSERVED RESULT
Applications are not listed in System Monitor if they are launched via shortcut (eg: Meta+E) or command line.

EXPECTED RESULT
No matter how apps are run, they should be listed in System Monitor.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-27-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

Comment 1 Nate Graham 2021-08-28 02:13:49 UTC

They key difference is whether or not the app is launched with its own cgroup, because the Applications page in System Monitor only knows about cgrouped apps. That's how it knows something is an app and not some random system process. When you run an app's binary directly (i.e you run `kate` inside a terminal window), it's up to you  to make sure that happens, since you're running the app by hand.

However when running an app via a global shortcut, this should be happening. I can reproduce the issue. Moving to the kglobalaccel framework.

Comment 2 David Redondo 2021-08-30 06:48:55 UTC

I thought we already a bug somewhere tracking this,
but it depends on if klauncher is runnign or not. If not we are using kstart5, probably should reverse that

Comment 3 David Redondo 2021-08-30 06:49:29 UTC


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