Bug 13871 - From custom disk partitioning onwards, the top layer guis are not screen-centered but left-aligned
Summary: From custom disk partitioning onwards, the top layer guis are not screen-cent...
Status: RESOLVED DUPLICATE of bug 12422
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 5alpha2
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-07 10:19 CEST by Dick Gevers
Modified: 2014-08-07 12:57 CEST (History)
0 users

See Also:
Source RPM: Classical isos 5a2
CVE:
Status comment:

Attachments
Top layer jumped left (37.74 KB, image/png)
2014-08-07 10:23 CEST, Dick Gevers 		Details
roughly the best looking position (52.45 KB, image/png)
2014-08-07 10:25 CEST, Dick Gevers 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Dick Gevers 2014-08-07 10:19:57 CEST 
Description of problem:

A number of guis are beautifullt in the centre of the screen.

But starting with Custom disk partitioning, when one is done with the first partition, the top layer guis jump almost completely to the left hand of the screen.

They can be centered back by grabbing with the mouse, but when the next partition has been handled, they jump back left again.

It would be nice to have them stay centered all the time. TIA


How reproducible: 
Install Mageia 5 Cauldron from iso and use Custom disk partitioning (I didn't try other means, as I don't want to wipe my other Mga install).


Steps to Reproduce:
as stated.

Reproducible: 

Steps to Reproduce:
Comment 1 Dick Gevers 2014-08-07 10:23:26 CEST 
Created attachment 5326 [details]
Top layer jumped left
Comment 2 Dick Gevers 2014-08-07 10:25:41 CEST 
Created attachment 5327 [details]
roughly the best looking position
Dick Gevers 2014-08-07 10:26:07 CEST

Whiteboard: (none) => 5alpha2

Comment 3 David Walser 2014-08-07 12:57:16 CEST 
duplicate of 12422

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.