Summary: | Solid always reports disk size in the form of GiB, regardless of the choice in systemsettings | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-solid | Reporter: | vyacheslav <galdralag> |
Component: | general | Assignee: | Lukáš Tinkl <lukas> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | adaptee, afiestas, cvnnxs, frank78ac, kdelibs-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Screenshot |
Description
vyacheslav
2012-01-29 14:26:36 UTC
I failed to reproduce it using KDE SC 4.9.0. The screenshot was missing. Is it still a problem for the reporter in KDE SC 4.9.0 ? Created attachment 73057 [details]
Screenshot
This bug still exists in KDE 4.9. Screenshot attached.
Thanks for your feedback. The screenshot helps clarifying where the problem is. Move it to the "places" component for now, although I guess it should be re-assigned to the kfile product. I think that these device names come from Solid. in kdelibs/solid/solid/backends/udisks/udisksdevice.cpp // Adapted from KLocale as Solid needs to be Qt-only static QString formatByteSize(double size) { ... } So it uses KiB/MiB/GiB in hardcoded way . *** Bug 313299 has been marked as a duplicate of this bug. *** Yup, confirmed. Solid is Qt-only code so it doesn't respect the user settings in this regard Maybe we should have some kind of backend mechanism for this but not going to happen until solid2. Setting as wish. This bug is reported on libsolid which is the kdelibs4 version of the solid library. It is now in maintenance mode. If you think it should still be fixed in the KDE Frameworks 5 version of solid please move it to or report a bug on frameworks-solid. A possibly relevant merge request was started @ https://invent.kde.org/frameworks/solid/-/merge_requests/153 |