Bug 498388 - System Monitor - kiB, MiB, GiB, TiB, PiB
Summary: System Monitor - kiB, MiB, GiB, TiB, PiB
Status: RESOLVED DUPLICATE of bug 453854
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: 6.2.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-08 14:40 UTC by vmelkon
Modified: 2025-01-08 16:42 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vmelkon 2025-01-08 14:40:45 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
This is a very old bug that doesn't get a fix although doing the fix would probably take 1 min.
System Monitor shows RAM usage and HDD usage or any storage as KiB, MiB, GiB, TiB, PiB, etc instead of obeying what the user has selected.
This bug has been fixed in Dolphin, Ark, Discover. See
https://bugs.kde.org/show_bug.cgi?id=57240

STEPS TO REPRODUCE
1. Open System Monitor
2. Look at the History section and Application section and all the sections
3. 

OBSERVED RESULT
System Monitor does not respect what is found in file
/home/xxxxx/.config/kdeglobals

at the line
[Locale]
BinaryUnitDialect=1   <====Notice the 1. This means JEDEC mode. This means 1024 B = 1 KB, 1024 KB = 1 MB

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-01-08 16:42:09 UTC
*** This bug has been marked as a duplicate of bug 453854 ***