Bug 907883 - Can't confirm custom partitioning layout having 800x600 screen
Summary: Can't confirm custom partitioning layout having 800x600 screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-05 13:21 UTC by Tomáš Bžatek
Modified: 2015-03-03 23:06 UTC (History)
6 users (show)

Fixed In Version: anaconda-19.14-1
Clone Of:
Environment:
Last Closed: 2013-05-12 17:15:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (77.54 KB, image/png)
2013-02-05 13:21 UTC, Tomáš Bžatek
no flags Details

Description Tomáš Bžatek 2013-02-05 13:21:53 UTC
Created attachment 693361 [details]
screenshot

Description of problem:
See the screenshot, it says it all. The overlay window "Manual partitioning" is shifted and having no decorations it can't be easily moved. Unfortunately it hides the most important button to save and apply the changes made.

The solution is to Alt+drag or Super+drag to move the window around and reveal the magic button. It can be reproduced consistently.

This is VMware Player 5.0, the X screen resolution is somehow automatically detected, giving me only 800x600.

Version-Release number of selected component (if applicable):
netinst ISO, F18 final

Comment 1 Chris Lumens 2013-03-26 15:22:39 UTC
Okay, I think this is because the Desired Capacity label and spinner next to it are too wide.  Pretty much any time you see the screen shifted like this, what it's telling you is that gtk can't fit all the widgets onto the screen in the layout we've requested, and this is the failure mode.

I see it most commonly with word wrapping being set wrong.

Comment 2 Tomáš Bžatek 2013-03-26 15:56:38 UTC
I don't think it's about a layout exceeding original window size, at least in this case it's about the window itself not being placed at [0, 0] but rather moved in the X axis.

It's been some time now but I vaguely remember moving the window manually and getting perfect fit for the screen.

Comment 3 Chris Lumens 2013-03-26 16:00:33 UTC
Having seen this several times now and fixing it by rearranging widgets and wrapping labels, I can assure you this is the failure mode for the window being too wide.

Comment 4 Adam Williamson 2013-05-12 17:15:57 UTC
Tested with F19 Beta TC3, confirmed fixed.


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