| Summary: | Numeric entry in New Partition dialog only allows whole numbers, thus Preferred Unit selection limits partition sizes. | ||
|---|---|---|---|
| Product: | [Applications] partitionmanager | Reporter: | Ryan Brown <ryan> |
| Component: | general | Assignee: | Andrius Štikonas <andrius> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | ilikefoss, ryan |
| Priority: | NOR | ||
| Version First Reported In: | 25.08.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | screenshot of Create a new partition dialog showing the default entries for a new partition on a 1.87 GiB gpt tabled device. | ||
Additional Information: Changing the Preferred Unit allows whole number entry in that size unit. Example: Changing Preferred Unit to MiB allows setting Size of the example partition above to values such as 1914.00 MiB which in turn would be much closer to the listed maximum size than the 1.00 GiB which would be the maximum via manual entry into the Size input. I can reproduce 2. where size in for some reason rounded down (when using GiB). Typing non-integer values works fine tough. I can type whatever non-integer value I want in e.g. size or start fields (perhaps you first need ot delete existing number) Decrement arrow for me works but it still adjust in MiB steps, so I have to click it 10 times for 2nd decimal digit to change. I think that QT / KDE software just hates the ones of us that want to see or to write more precision: https://bugs.kde.org/show_bug.cgi?id=498820 As a power user and developer I hate that I cannot see or write more precision or even better, customize the level of precision that I like to see or write. A lot of things seem to have been just dumbed-down. I remember that I also tried to make partitions without changing to MiB, but I couldn't, so I was forced to use MiB and then use DuckDukGo to make all the necessary conversions. Which is something that I hate as it wastes time and every time a software forces me to use the internet to solve something, I get a bad impression of that software. I should be able to do everything locally with the software that I have. I know that I can use KCalc to many all the necessary conversions but multiplying or dividing with 1024, but it's still wastes times and I'm never sure if I converted well between TiB or GiB and MiB. Please let us use as many digits as we need / want after the floating point! |
Created attachment 187166 [details] screenshot of Create a new partition dialog showing the default entries for a new partition on a 1.87 GiB gpt tabled device. SUMMARY The New Partition dialog has three (3) numeric entry inputs. Each input shows two decimal places, but only allows whole numbers. The sizes entered here are thus limited to whole numbers of the Preferred Unit as selected in the Advanced Settings. This restriction also seems to apply to defaulted/automatic values in some cases. STEPS TO REPRODUCE 1. with device with unallocated space, initiate the New partition dialog (click new button or context menu item) Preferably the unallocated space is not a whole number of the current Preferred Unit. 2. Observe the Size value will be automatically set to the rounded down whole number of the available space rather than the near actual space to the indicated two(2) decimal places. Note that the Visual display above shows the intended size. 3. Creating the partition: a. If the user does not try to alter the amounts and clicks "OK" then the size of the partition is as the default should be. This indicates that the size input has the proper value, but incorrectly does not display it. b. If the user tries to alter the value of the size several different things can happen: - using the example of a 1.87GB drive the initial values show Free space before: 0.00 GiB, Size: 1.00 GiB, Free space after: 0.00 GiB -- Set focus to the Size input and type "1.2": the "1" replaces the existing number, now showing "1 GiB" with cursor after the "1". the "." is added, now showing "1. GiB" cursor after the ".", Typing the "2" results in no changes as the 2 is not added. A zero is permitted to be added however. -- (again from start) Using the decrement arrow once reduces the size shown in the visual representation from 1.87 GiB to 1,023.00 MiB, the Size input is unchanged until the size changes from 1019.00 MiB to 1018.00 GiB then shows 0.99 GiB and the Free space after input changes to show 0.87 GiB, the increment arrow on the Size input is now enabled. Using the increment operation (either with the button or the up key on a keyboard) the size can be increased until 1.00 GiB but no further. -- Using the mouse pointer to move the visual representation's handles (either size of the new partition) does allow the size to be changed as expected. During the size change in this way, the Size and Free space inputs show values as expected. OBSERVED RESULT Unable to change numeric inputs directly except by whole numbers, using increment & decrement operations of an input allows finer grained changes, but the increment is capped at the floor of the available size. EXPECTED RESULT The default value should show the actual value with the indicated two decimal places. Should be able to change the size to a valid value (between Min and Max size) using the keyboard to type in a value with non-zero decimal values. Should be able to use the increment operation of a numeric input to increase to the actual maximum value rather than the floor (rounded down whole number) of the maximum value. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.0 Kernel Version: 6.17.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4670K CPU @ 3.40GHz Memory: 32 GiB of RAM (31.3 GiB usable) Graphics Processor: NVIDIA GeForce RTX 2060 ADDITIONAL INFORMATION