- Oct 08, 2020
-
- Oct 01, 2020
-
-
ahiemstra authored
They were apparently missing units.
-
- Sep 24, 2020
-
-
l10n daemon script authored
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"
-
l10n daemon script authored
-
- Sep 19, 2020
-
-
l10n daemon script authored
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"
-
l10n daemon script authored
-
- Sep 18, 2020
-
-
l10n daemon script authored
-
- Sep 17, 2020
- Sep 16, 2020
-
-
Laurent Montel authored
-
- Sep 15, 2020
-
-
ahiemstra authored
ksystemstats expects sensors to consist of at least three parts: subsystem, object, property. Sensors like "system/processors" break this assumption, causing them to not be properly readable. Rather than trying to come up with an elaborate way to handle this in ksystemstats, simply expose them also as a three-part sensor so the mapping doesn't need to change. These sensors are not very dynamic anyway so duplicating them does not do much harm. The two-part version is kept around for backward compatibility with the ksysguard UI.
-
- Sep 03, 2020
-
-
David Redondo authored
Clients and plugins are both children of the daemon. The Client destructor dereferences SensorProperties to unsubscribe from them. Because usually the object tree looks something like plugin -> sensorcontainer -> sensorobject -> sensorproperty we can not rely on the properties still being around when the clients are deleted. This fixes the segfault in the unit test detected by the address sanitizer.
-
adridg authored
The label can be edited in the dialog, but this information wasn't being set again on the footers in the graph display. BUG: 373935
-
adridg authored
-
adridg authored
In the table of sensors (for bar charts) show the label in column 1 (second, right after host) rather than hiding it at the end; this makes it easier to distinguish the sensors which are **typically** all "localhost, System/CPU Lo.../, %" and then the UI is cut off (scroll right to see the remaining columns, including label).
-
adridg authored
-
David Redondo authored
The returned map also contains infos about containers and objects.
-
- Sep 01, 2020
-
-
jriddell authored
GIT_SILENT
-
- Aug 31, 2020
-
-
David Redondo authored
Saves parsing all these files in /proc/net. For now the old code path is retained as fallback when there is some error communicating with the kernel.
-
- Aug 14, 2020
-
-
ahiemstra authored
Unconnected devices do not have any useful data we can expose, so simply hide them completely instead of showing devices that do not provide useful data.
-
- Aug 13, 2020
-
-
David Redondo authored
The return value of compare is 0 if both strings match https://en.cppreference.com/w/cpp/string/basic_string/compare
-
- Aug 03, 2020
-
-
DavidEdmundson authored
If ksgrd changes the monitors then all IDs are invalid. This can happen when a new device is plugged in and removed. SensorObjects can remain valid and are re-matched up.
-
- Jul 31, 2020
-
-
David Redondo authored
-
Laurent Montel authored
-
- Jul 30, 2020
- Jul 29, 2020
-
-
ahiemstra authored
As it turns out, DeviceStatistics does not update monotonuously, so we end up without updates that would reset the update rate to 0 or otherwise miss data. So instead, use an internal timer that queries the statistics object regularly and use that data for the upload/download sensors.
-
ahiemstra authored
Similar to the old aggregate sensors but now in a different place.
-
ahiemstra authored
-
ahiemstra authored
-
ahiemstra authored
-
ahiemstra authored
The NetworkManager backend is preferred, let's see if this causes actual problems first before adding another backend.
-
ahiemstra authored
It has now been replaced by a new plugin that uses NetworkManager.
-
ahiemstra authored
-
ahiemstra authored
Otherwise we end up with all sensor names being prefix with a space.
-
ahiemstra authored
Otherwise we still get updates for things that should have been removed.
-
ahiemstra authored
Otherwise you end up with thinking things are running while they are not.
-
ahiemstra authored
It is set up to be able to handle different backends, though for the moment only the NetworkManager backend is functional.
-