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: | ||
Sentry Crash Report: |
Description
hsnnsnc
2021-08-27 20:37:27 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. 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 *** This bug has been marked as a duplicate of bug 433362 *** |