Bug 445011 - firstboot Forward button broken
Summary: firstboot Forward button broken
Keywords:
Status: CLOSED DUPLICATE of bug 442394
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-02 18:42 UTC by Warren Togami
Modified: 2008-07-31 17:49 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-07-31 17:49:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Screenshot (195.51 KB, image/png)
2008-05-02 18:42 UTC, Warren Togami
no flags Details

Description Warren Togami 2008-05-02 18:42:41 UTC
Date and Time page of firstboot and Timezone tab.  The Forward button is broken
in that it doesn't go forward.  It seems to toggle the "System clock uses UTC"
checkbox.

Comment 1 Warren Togami 2008-05-02 18:42:41 UTC
Created attachment 304404 [details]
Screenshot

Comment 2 Chris Lumens 2008-05-06 17:56:06 UTC
Yeah this is because of your screen resolution.  What's the hardware involved
that requires running in such a small amount of space?

Comment 3 Warren Togami 2008-05-06 18:10:52 UTC
Both KVM and several boxes (Thinkpad T41 with Radeon 7500, and Dell Xeon
workstations with nv Quadro) with 1024x768 or 1680x1050 LCD monitors apparently
run firstboot at 800x600 before auto-configuring to native resolution.  I
actually haven't seen firstboot run at a non-800x600 resolution in the past few
weeks.

Comment 4 Chris Lumens 2008-05-12 15:23:47 UTC
Do you use rhgb or not?

Comment 5 Warren Togami 2008-05-12 15:40:50 UTC
rhgb yes.


Comment 6 Bug Zapper 2008-05-14 10:32:30 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Chris Lumens 2008-07-31 17:49:28 UTC

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


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