Bug 15474 - disk partitioning tool on Mga5-b3 almost unuseable
Summary: disk partitioning tool on Mga5-b3 almost unuseable
Status: RESOLVED DUPLICATE of bug 15272
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-12 06:43 CET by w unruh
Modified: 2015-03-14 20:55 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description w unruh 2015-03-12 06:43:16 CET
Description of problem: Dell XPS13 2015 edition. Trying to install Mageia 5 B3. The disk partitiong window (Customize) does not show any paritions. If I then select sdb it shows the partition on that (a usb stick) and when I come back to sda it now shows the partition. 

However, the width of the partition display increases as I choose items, so that the option get squeezed off the side. I cannot read any of the labels on the action buttons, making it almost impossible to do anything. Since I created the partitions in Windows I have to change the type, but cannot do so since I cannot read the buttons in expert mode. 





How reproducible: Always (well I tried twice)


Steps to Reproduce: put in MGA5 B2 x86 on usb stick into computer, boot, choose install, get to disk partitioning, choose customize, and the above happens. 

It is as if MGA thinks the screen is wider than it is. However the "Toggle to expert mode", Auto Allocate", "More" and "Done" buttons are fine. It is just the
stuff inside the partitions window that is problematic.






Reproducible: 

Steps to Reproduce:
Comment 1 w unruh 2015-03-12 06:57:26 CET
Note-- I have 10 partitions on that disk (It is a UEFI disk) -- ranging in size from a few MB to 50GB. I think that the partitioning program is misallocating the length of space to assign to the partition display, and squeezing out the buttons. Instead one should make sure that the bottons have enough room allocated, and then the partition display be squeezed into the space left over.
The current situation makes it impossible to partition the drive. 
The only thing I can do is to pull the plug on the installation.
Comment 2 Sander Lepik 2015-03-12 10:03:55 CET
Seems to be duplicate.

*** This bug has been marked as a duplicate of bug 13679 ***

Status: NEW => RESOLVED
CC: (none) => mageia
Resolution: (none) => DUPLICATE

Comment 3 w unruh 2015-03-14 17:14:14 CET
While the comment in the first sentence (no partitions showing under custom partitioning for first disk) is a duplicate of bug 13696, the second part is not.
I was installing Mageia 5 B3 onto a UEFI computer (Dell X13 2015 edition) and the screen came up with very large letters ( might have been 640x480 or something like that). Under custom partitioning when I tried to create new partition, (once I got them to display by clicking on sdb and then sda) the buttons telling me my options as to what to do with that partition were off the side of the screen, and I could only see about 1/3 of them. It seems that the system was expanding the 
partition table and squeezing out the buttons. This made it really really hard to partition the empty space on the disk. 

When I later installed by using the isodumper program so that  it came up in UEFI mode, the screen resolution was large (probably close to the 1900 native resolution of the screen) and I had no such problem. Ie, it seems to be a problem if the installer has to drop down to some minimal screen mode. If there are many partitions on the disk (I have 10) the custom partitioning program has space trouble and squeezes off the buttons off the right side of the screen.

Status: RESOLVED => REOPENED
Resolution: DUPLICATE => (none)

Comment 4 Marja Van Waes 2015-03-14 20:55:43 CET
The other issue is  bug 15272, you can test the fix with boot.iso

*** This bug has been marked as a duplicate of bug 15272 ***

Status: REOPENED => RESOLVED
CC: (none) => marja11
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.