453854 2022-05-15 20:36:20 +0000 Please follow BinaryUnitDialect, appropriately 2026-02-25 02:54:45 +0000 1 1 3 Frameworks and Libraries ksystemstats General unspecified Gentoo Packages Linux RESOLVED FIXED https://bugs.kde.org/show_bug.cgi?id=364321 HI wishlist --- 57240 1 bugs.kde.org plasma-bugs-null 4wy78uwh ahiemstra andreas_nordal_4 daninshed dave jrb3218 kde kde_bugtracker.3o1kp mtjhrj nate plasma-bugs-null vmelkon wanderer510 zakhar.nasimov zdenek.koprivik https://invent.kde.org/plasma/libksysguard/-/commit/9ddde2299063fdbf941858c46eef5acafc20103a 6.7.0 0 oldest_to_newest 2123636 0 bugs.kde.org 2022-05-15 20:36:20 +0000 SUMMARY The system monitor does not seem to follow the BinaryUnitDialect config option. Likely it is just a matter of replacing some function with some higher-level ones, as other apps do the right thing (e.g., Krusader). STEPS TO REPRODUCE 1. Set BinaryUnitDialect=2 in [Locale] section of $KDEHOME/.config/kdeglobals (setting to metric/SI instead of IEC) 2. Start system monitor 3. Look at some of the stats showing OBSERVED RESULT IEC formatting is used everywhere instead of metric EXPECTED RESULT Metric formatting is used everywhere it is appropriate (I think the only place IEC might make sense is for memory size and usage when a preference for metric is expressed) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION The BinaryUnitDialect config option is described in Bug 57240. This option is for now still without a GUI, but Bug 364321 makes it clear this is about to change. So apps like the system monitor should be made ready to follow BinaryUnitDialect. 2124022 1 vmelkon 2022-05-17 03:37:30 +0000 I have tested this on Kubuntu 22.04 I can confirm that I have the same result. KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 I have tried BinaryUnitDialect=2 and BinaryUnitDialect=1. In both cases, KSysGuard just ignores it and keeps on showing kiB, MiB, GiB, TiB. 2201353 2 nate 2023-01-24 18:28:00 +0000 *** Bug 464604 has been marked as a duplicate of this bug. *** 2201680 3 kde 2023-01-25 10:22:48 +0000 There is no UI for this setting and seems it is not even global, only KIO reads it https://lxr.kde.org/search?%21v=kf5-qt5&_filestring=&_string=%22BinaryUnitDialect%22 2201733 4 bugs.kde.org 2023-01-25 12:11:17 +0000 (In reply to David Redondo from comment #3) > There is no UI for this setting That is the topic of the linked bug report: https://bugs.kde.org/show_bug.cgi?id=364321 This is a chicken-and-egg problem: as long as applications to not support it, the value of a GUI is limited and developers will not find it urgent, and application developers will point to the lack of a GUI to say that it is not urgent > it is not even global, only KIO reads it I cannot comment on this. I guess that means it is harder to implement? AFAIU previously, it was just a matter of using existing framework functions that do support it. Then perhaps a new bug report is in order to request for better support for this in a framework. 2216369 5 nate 2023-03-14 19:57:35 +0000 *** Bug 467317 has been marked as a duplicate of this bug. *** 2231033 6 nate 2023-05-16 23:48:32 +0000 *** Bug 391596 has been marked as a duplicate of this bug. *** 2242070 7 nate 2023-07-21 21:34:56 +0000 > AFAIU previously, it was just a matter of using existing framework functions that do support it That's correct, yes. The frameworks-provided function has been fixed to read the setting properly; see https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/352. Now System Monitor just needs to use it and then this will get fixed automatically. 2250680 8 nate 2023-09-05 19:47:49 +0000 *** Bug 474155 has been marked as a duplicate of this bug. *** 2252427 9 andreas_nordal_4 2023-09-11 22:40:31 +0000 Is it a good idea to use the same configuration for everything? There may be opposite conventions to follow: For network speed, I would even suggest that if the configuration isn't SI, the configuration is wrong. But opposite for memory and partition sizes. Not that I would argue for more options. Rather that getting the default right in each case without not making the user choose between two wrongs is more important. 2253383 10 vmelkon 2023-09-16 03:38:00 +0000 Good idea. "Not that I would argue for more options. Rather that getting the default right in each case without not making the user choose between two wrongs is more important." >>I would argue for more options. Nothing wrong with more options, as long as it is documented somewhere. After all, Microsoft documents their registry keys and someone publishes 500 page books on Windows Server. If Microsoft can program a feature, then so can anyone. (In this case, Windows doesn't have such features). 2387771 11 nate 2025-01-08 16:42:09 +0000 *** Bug 498388 has been marked as a duplicate of this bug. *** 2391988 12 ahiemstra 2025-01-23 14:37:56 +0000 *** Bug 497160 has been marked as a duplicate of this bug. *** 2391990 13 nate 2025-01-23 14:38:38 +0000 *** Bug 494955 has been marked as a duplicate of this bug. *** 2405029 14 nate 2025-03-05 17:24:44 +0000 *** Bug 501065 has been marked as a duplicate of this bug. *** 2447006 15 zdenek.koprivik 2025-08-13 09:54:25 +0000 There is now UI for setting this option in System Settings, but System Monitor still ignores it. 2487759 16 bug-janitor 2026-01-23 15:49:19 +0000 A possibly relevant merge request was started @ https://invent.kde.org/plasma/libksysguard/-/merge_requests/460 2496277 17 nate 2026-02-19 15:43:32 +0000 Git commit 9ddde2299063fdbf941858c46eef5acafc20103a by Nate Graham, on behalf of David Redondo. Committed on 19/02/2026 at 15:43. Pushed by ngraham into branch 'master'. Follow the user preference when formatting byte values Use the binary formatting option selected by the user in system settings. FIXED-IN: 6.7 M +1 -0 formatter/CMakeLists.txt M +109 -42 formatter/Formatter.cpp https://invent.kde.org/plasma/libksysguard/-/commit/9ddde2299063fdbf941858c46eef5acafc20103a 2498192 18 nate 2026-02-25 02:54:45 +0000 *** Bug 475459 has been marked as a duplicate of this bug. ***