Bug 426308 - Wrong units for read and write throughput when disk is plugged after ksysguard start
Summary: Wrong units for read and write throughput when disk is plugged after ksysguar...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (show other bugs)
Version: 5.18.4
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-08 11:49 UTC by JPT
Modified: 2024-09-23 21:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description JPT 2020-09-08 11:49:36 UTC 
The units shown for read and write throughput show wrong units if the disk was plugged after ksysguard was started. This problem exists for at least five years.

STEPS TO REPRODUCE
1. start ksysguard
2. for initial set up: attach disk, so the sensors appear
3. for initial set up: add "read" or "write data" sensors 
4. remove disk
5. maybe reboot/relogin necessary
6. start ksysguard
7. attach disk
8. for correct display restart ksysguard

OBSERVED RESULT
now it shows wrong units (and values?) for the sensors. 

EXPECTED RESULT
Units MiB/s or KiB/s

SOFTWARE/OS VERSIONS
Linux: 5.4.0-47-generic 64 bit
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
btw, it also shows wrong label, at least in the german translation. it shows read and write accesses instead of throughput/data, see also bug #425489
Comment 1 Christoph Cullmann 2024-09-23 21:00:19 UTC 
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task.

If your issue still happens with the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!