Created attachment 568074 [details] Picture of problem Description of problem: When entering up the firstboot anaconda installer component, the buttons near the bottom of the window are positioned off the screen. This may be due to multiple monitors. This is better than in FC16, where the anaconda installer tried to span multiple monitors. However it'll still be confusing to users, who won't know how to alt-drag the window upwards to get to the buttons. Version-Release number of selected component (if applicable): FC 17 Alpha How reproducible: First boot only runs once. Actual results: No buttons visible by default. Expected results: Buttons should be usable. Additional info:
What window manager did you install? metacity, kwin, xfwm4, or openbox?
This is Fedora 17 Alpha, and I didn't customize the install at all. So the window manager installed would be mutter (ie: gnome-shell).
Stef on irc said he has multiple monitors of slightly different dimensions. This means the X screen size is probably larger than the monitor firstboot is displayed on. The code has this: self._y_size = gtk.gdk.screen_height() and later self.leftEventBox.set_size_request(leftWidth, self._y_size) So that would explain this. It probably needs to query the dimensions of the appropriate monitor instead of the overarching screen.
*** Bug 753985 has been marked as a duplicate of this bug. ***
firstboot-17.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/firstboot-17.2-1.fc17
Package firstboot-17.2-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing firstboot-17.2-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-6318/firstboot-17.2-1.fc17 then log in and leave karma (feedback).
firstboot-17.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.