How do you mean it is technically correct? Other tools would generally accept "1.5 GB", "1.5 G" or "1.5g" as valid input for file size, depending on syntax. Qemu-img, for example (being of similar function to this part of the VirtualBox control console), would accept 1.5G or 1.50G interchangeably as a valid file size for a new virtual disk.
Basically, my point boils down to this: 1.5 equals 1.50. 1.5 does not equal 1.05. So this is a bug. Perhaps I'm filing the bug in the wrong place? Should this instead be filed with the VirtualBox project? -- Image Size broken in VirtualBox OSE https://bugs.launchpad.net/bugs/245923 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
