plasma-systemmonitor in kdereview

[Harald Sitter]

On 01.10.20 14:36, Arjen Hiemstra wrote:
> On Thursday, 1 October 2020 14:11:16 CEST Harald Sitter wrote:
>> On 01.10.20 11:36, Arjen Hiemstra wrote:
>>> Hello,
>>>
>>> I'd hereby like to announce that plasma-systemmonitor is in kdereview. It
>>> can be found at https://invent.kde.org/plasma/plasma-systemmonitor .
>>>
>>> plasma-systemmonitor is a new system monitor UI built with Kirigami. It
>>> makes use of the ksystemstats daemon and the faces system for system
>>> monitor plasmoids that were both introduced in Plasma 5.19.
>>>
>>> Our current plan is to do a "preview release" alongside Plasma 5.20, then
>>> have it be an official part of Plasma with 5.21.
>>
>> Cool stuff.
>>
>> L10n is currently a bit incomplete.
>> Notably
>> - the pages files lack any localization at all and I'm also not sure how
>> those could be best localized.
> 
> Yeah that is a good point. If we can somehow extract the strings from these 
> files I think we can make it work. But that may need some custom scripting.
> 
>> - the 'configure columns' feature doesn't load the translated strings
>> into the checkboxes
> 
> Huh, weird. They are being populated by i18n calls, wonder what's going on 
> there.

I also couldn't spot what's going wrong FWIW. There was a problem with
strings getting loaded before the domain was set up or something with
qml plugins. Maybe it's that problem? OTOH why would that affect the
combobox but not the labels. It's very odd indeed.

>>
>> On the subject of configure columns I feel like word wrapping would look
>> better than eliding there https://i.imgur.com/RbAeUhH.png
>>
>> Something is astray with memory calculation. See konsole which is
>> somehow listed as 2.6gib https://i.imgur.com/MjIpj3O.png but its actual
>> children aren't getting nowhere near that number. I'm guessing it's
>> because even detached processes (notably vscode here) are in the same
>> cgroup? If so we probably can't do much about this?
>>
> 
> There's two things going on here I expect: everything started from konsole 
> will be part of the konsole cgroup unless started through kstart5 or a similar 
> tool that explicitly moves things to a new cgroup. I doubt this is solvable 
> without patching all major shells. 
> 
> The other thing is that the "memory" column here is what is called "Total 
> Memory" in KSysGuard, which is the process' private memory with the shared 
> memory added divided over the processes that share that memory. This provides 
> a more accurate number for the actual memory usage of the process, but does 
> mean that it will most likely seem like it suddenly uses more memory, since 
> the "memory" in KSysGuard is only the private memory.

Makes sense.
Maybe we should blacklist konsole or something ^^
I'm almost certain people are going to look at it and go "gosh, konsole
is fat" and then turn to their forum of choice and lament how terribly
inefficient our software is.

>> Sometimes the CPU column shows nan% for new apps. Happens a lot with
>> bustle for me. In fact, sometimes I have two entries one of which is
>> nan% for all eternity https://i.imgur.com/HLavLsI.png
> 
> The lingering one is odd, but may have something to do with cgroups not 
> getting cleaned up properly. If you can reproduce and provide the output of 
> systemd-cgls that would be helpful.

│   ├─user at 1000.service
│   │ ├─app.slice
│   │ │ ├─app-org.freedesktop.Bustle-c200626490444a60b898eb65b179d6f7.scope
│   │ │ │ ├─216216 bwrap --args 31 bustle
│   │ │ │ ├─216224 bwrap --args 31 bustle
│   │ │ │ └─216225 bustle
│   │ ├─flatpak-org.freedesktop.Bustle-216216.scope
│   │ │ ├─216221 bwrap --args 31 xdg-dbus-proxy --args=33
│   │ │ └─216222 xdg-dbus-proxy --args=33

Mind you, both are cleaned up on exit and the second one doesn't always
appear to begin with.

>> Also the columns in the processes page lack labels.
> 
> Gah. And applications works correctly?

Yup.

HS