GitLab

This file was accidentally omitted when deleting the contents of the smaps folder when porting detailed memory information to QtWidgets.

Eugene Popov authored May 11, 2022 and Arjen Hiemstra committed May 11, 2022

Currently, the detailed memory information is displayed as a web page,
and this has several limitations:

* it's not possible to filter data
* it's not possible to sort data by a specific column
* it's not possible to move columns
* it's quite slow and looks outdated

Porting it to QtWidgets removes these limitations and adds new features:

* general page: shows general information about process
* memory maps page: shows memory consumption for each of the
  process's mappings
* open files: shows files opened by the process

I think this is leftover from earlier code where we would track which
preset is active.

The three sensor properties of FaceController contain the resolved
sensors. This means we are not writing group regular expressions to face
presets but are wiriting only the local sensors that were found for that
group, pretty much bypassing why we have the groups in the first place.
The unresolved sensors are only contained in the sensor configuration,
so read them from there and write that to the preset faceproperties.

When loading presets we expect the faceproperties file to be located in
"contents/config/" but when writing we are placing it in "contents/"
which means that custom presets are not loaded properly.

BUG: 450745

BUG:452248

Some power sensors don't expose a current value most notably amdgpu.
For those fall back to the average reading if available.
BUG:445920

Trent McPheron authored May 05, 2022 and Arjen Hiemstra committed May 05, 2022

I noticed that the current version of the horizontal bars face does not meaningfully present any values that are lower than its own height, including zero, which is problematic for sensors that can be regularly expected to show low values, such as total CPU usage and swap space usage. For sensors like these, it would always draw a circle of width equal to its own height as a minimum value, which completely throws away any nuance at the low end, including the ability for the bar to represent zero at all. This problem is especially noticeable when you place a horizontal bars sensor on a thin vertical panel.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

GIT_SILENT

No longer needed after 84ade540.

Also enables the Qt6 Linux CI.

The plugin relies on its parent to be `KSysGuard::Processes`.

Regression from d4d8a5a2

BUG: 451148

John Fano authored Feb 28, 2022 and Nate Graham committed Feb 28, 2022

The current calculation method for the bar chart spacing
would always result in a spacing size of zero (0).  This fix
implements a fixed size bar spacing scaling with the font size.
It allows the chart to scale well at any resolution, DPI and
font size as well as with any number of items charted.

BUG: 449868
FIXED-IN: 5.24.3

Before:

org.kde.ksysguard.plugin.network: Helper process terminated abnormally!
org.kde.ksysguard.plugin.network: "The process doesn't have permission to open the capture source\n"

After:

org.kde.ksysguard.plugin.network: Helper process terminated abnormally: "The process doesn't have permission to open the capture source"

GIT_SILENT

This is not so much about dead code optimizations as about general
sanity of conditional compilation.

GIT_SILENT

That is some Unicode bullet character. There's not way it is Latin1.

This commit partially reverts cbf8f29c.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

This is a porting mistake from commit 0c76e685, thanks to Luke Horwell
for finding the guilty commit. For more details see:
!200