Opened 4 years ago

#11872 new bug

Inconsistency between reported partition size value and actual partition size value

Reported by: kushalsingh007 Owned by: stippi
Priority: normal Milestone: R1
Component: Applications/DriveSetup Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

While trying to create a partition (after initializing partition map) when the user tries to take the offset bar to the left most extreme , then even though the partition size is zero, since the offset reported in the text box is zero, the value displayed is non-zero. Once taken to the left most extreme then even on typing the value of offset as zero the partition size value is reported incorrectly. But if the offset is moved to somewhere else other than left most extreme , then on typing the value 0 in the offset text box the correct value gets displayed. This bug can be easily reproduced with large sized drives. In my case I had a 2TB (virtual) drive and I was trying to create a partition with 1TB space in the partition map.

Attachments (1)

Screenshot from 2015-02-23 03:41:30.png (181.4 KB) - added by kushalsingh007 4 years ago.
Screenshot showing the inconsistency between the actual and reported values.

Download all attachments as: .zip

Change History (1)

Changed 4 years ago by kushalsingh007

Screenshot showing the inconsistency between the actual and reported values.

Note: See TracTickets for help on using tickets.