| Summary: | A way to navigate from an "app" to its process root | ||
|---|---|---|---|
| Product: | [Applications] plasma-systemmonitor | Reporter: | Ilya Bizyaev <bizyaev> |
| Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | ahiemstra, aspotashev, nate, notmart, plasma-bugs-null |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 5.27.10 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Ilya Bizyaev
2024-01-02 23:53:11 UTC
The problem with this is that it is not known what the "root process" is. The application filtering happens based on CGroups, which have no concept of "root process". We could try going to the first process in a group but that is often a launcher script or program, not the process which one would really consider "root". Additionally, as soon as you switch to the processes page you lose any context of the application. I think it would be better to have some way of displaying the processes of a group clearly, either by some advanced filtering in the process table or by enhancing the process details in the information pane. I'm going to close this since we now combine duplicate entries into a single "applications" entry, which means it has become completely impossible to determine the "root process" of an application. |