Bug 493153 - Both the back and next buttons are not visible on the partition screen in liveinst
Summary: Both the back and next buttons are not visible on the partition screen in liv...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 11
Hardware: i686
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-31 19:50 UTC by sgodsell@hotmail.com
Modified: 2009-06-25 17:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-25 17:40:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description sgodsell@hotmail.com 2009-03-31 19:50:12 UTC
Description of problem:
   On netbooks with a display of 1024x600 you cannot see the back and next
   buttons when you get to the partition screen.

Version-Release number of selected component (if applicable):
   Beta Fedora 11


How reproducible:
   Get a netbook and run it.  You will see for yourself ;-)


Steps to Reproduce:
1. liveinst
2.
3.
  
Actual results:
   Cannot see the back and next buttons

Expected results:
   Be able to see the back and next buttons

Additional info:

Comment 1 Jeremy Katz 2009-04-03 17:30:25 UTC
If you go into the fonts tab of the appearances settings (System->Preferences->Appearances->Fonts) and then click on the details, what's the DPI set to?

Comment 2 Peter Robinson 2009-04-04 19:38:28 UTC
On my eeePC 901 which has a 1024x600 screen as well and is seeing the same issue the dpi is 134.

Comment 3 Jeremy Katz 2009-04-08 15:56:01 UTC
Fix is under review and will be in rawhide in a day or two

Comment 4 Bug Zapper 2009-06-09 12:53:14 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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