Summary: | Don't show Applications view at all when the system doesn't support systemd cgroups | ||
---|---|---|---|
Product: | [Applications] plasma-systemmonitor | Reporter: | Andreas Sturmlechner <asturm> |
Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | ahiemstra, aspotashev, b_power, moondrake+kde, nate, ostroffjh, plasma-bugs-null |
Priority: | LO | ||
Version First Reported In: | 5.23.90 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | screen shot |
Description
Andreas Sturmlechner
2022-01-26 11:53:47 UTC
Seems reasonable; in this case we're just torturing the user. It's not really technically feasible currently though, support is currently determined by the model used for the table, which is deep down in the page structure and isn't really accessible by other parts. Moreover, the page loading code lacks any form of conditional loading, it simply looks at which pages exist and shows those. We'd have to special case stuff for the applications page which gets ugly fast. Created attachment 146944 [details]
screen shot
Comment on attachment 146944 [details]
screen shot
Get this on a Rocky Linux (KVM/QEMU) VM too...
Operating System: Rocky Linux 8.5
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 4.18.0-348.12.2.el8_5.x86_64 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel Core Processor (Haswell, no TSX, IBRS)
Memory: 7.6 GiB of RAM
Graphics Processor: llvmpipe
Host:
Operating System: Rocky Linux 8.4
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
Kernel Version: 4.18.0-305.25.1.el8_4.x86_64
OS Type: 64-bit
Processors: 12 × Intel® Xeon® CPU E5-2620 v3 @ 2.40GHz
Memory: 31.1 GiB of RAM
i.e. getting it on a systemd system. (In reply to Arjen Hiemstra from comment #2) > It's not really technically feasible currently though, support is currently > determined by the model used for the table, which is deep down in the page > structure and isn't really accessible by other parts. Moreover, the page > loading code lacks any form of conditional loading, it simply looks at which > pages exist and shows those. We'd have to special case stuff for the > applications page which gets ugly fast. eh, we had a nice view of applications for 30 years or so, but now its not feasible? I do not mind support for new APIs but it does seem a bit harsh to simply throw out the previous implementation that did what it had to do. |