https://bugs.kde.org/show_bug.cgi?id=450810
Niccolò Venerandi <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC| |[email protected] --- Comment #11 from Niccolò Venerandi <[email protected]> --- This should be fixed since KDE Frameworks 6.3. Apps used to be started first and moved into their own systemd scope afterwards, so an app whose launcher forks and exits right away (like Skype's or VS Code's) could leave its real process behind in plasmashell's cgroup. Since https://invent.kde.org/frameworks/kio/-/merge_requests/1622, apps launched from Plasma are started as transient systemd services, which systemd spawns directly in the app's own cgroup. I can't reproduce it anymore on current git master: a pinned launcher that forks and exits always ends up in its own app-….service. If you still see it with Frameworks 6.3 or later, please reopen. -- You are receiving this mail because: You are watching all bug changes.
