Bug 504912

Summary: Application view does not list some applications (VS Code)
Product: [Applications] plasma-systemmonitor Reporter: Massimiliano L <m.lincetto>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED NOT A BUG    
Severity: normal CC: ahiemstra, nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 6.3.5   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Massimiliano L 2025-05-28 13:40:10 UTC 
SUMMARY
The Applications tab does not list some applications. So far, I could identify 

STEPS TO REPRODUCE
1. Install and run VS Code
2. Open System Monitor
3. Open Applications view

OBSERVED RESULT
VS Code is not listed as an application but several "code" processes appear under Processes.

EXPECTED RESULT
VS Code is listed as an application.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 14 × Intel® Core™ Ultra 5 125U
Memory: 15.1 GiB of RAM
Graphics Processor: Intel® Graphics
Manufacturer: LENOVO
Product Name: 21MMS7CK00
System Version: ThinkPad T14 Gen 5

ADDITIONAL INFORMATION
- At a quick glance, I don't see other applications that are not listed.
- Mission Center correctly lists VS Code as application.
Comment 1 Nate Graham 2025-05-28 15:51:24 UTC 
How did you launch the app? Did you do it using a terminal window?
Comment 2 Massimiliano L 2025-05-28 20:36:37 UTC 
(In reply to Nate Graham from comment #1)
> How did you launch the app? Did you do it using a terminal window?

This is it, indeed. If I launch it from the KDE menu, it shows up under Applications.

I am used to `cd` into a directory and launch `code` from it.
Comment 3 Nate Graham 2025-05-28 20:38:35 UTC 
That's the cause, then. :) Apps can only get marked as applications when launched using a tool that puts them into a cgroup calling the binary directly won't do that.

If you launch it using `kstart code`, it should work.