Bug 741204 - dual head: anaconda sets resolution for both displays
Summary: dual head: anaconda sets resolution for both displays
Status: CLOSED DUPLICATE of bug 725219
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-09-26 09:22 UTC by Šimon Lukašík
Modified: 2011-10-13 08:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-09-26 13:15:21 UTC

Attachments (Terms of Use)

Description Šimon Lukašík 2011-09-26 09:22:58 UTC
Description of problem:
I tried to install Fedora 16 from 2011-09-23. I have dual head setup
with one monitor smaller than the other.

    VGA1 1680x1050 on the left
    LVDS1 1280x800 on the right and top

The anaconda graphical installer sets the resolution to


which means that anaconda screen is divided into two monitors, which
looks quite ugly. Moreover, the <next> buttons are not visible on my

Version-Release number of selected component (if applicable):
Fedora 16 from 2011-09-23, Rawhide.

How reproducible:
Actual results:
The resolution is set max sum, according to capabilities of each display.

Expected results:
The resolution should be set to one of the screen.

Additional info:
This is a regression against Fedora 14 and Fedora 15.

Comment 1 Chris Lumens 2011-09-26 13:15:21 UTC

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

Comment 2 dinyar.rabady+spam 2011-10-13 08:48:05 UTC
I had this problem too when installing on a dual-head setup. Navigating forward was only possible through guesswork (I hit TAB an "appropriate" number of times to get where I thought "next" would be. It is something that should be fixed before release.

I'm also not sure this is really a duplicate as it only affects installation. (and only on Fedora 16 iirc - I don't think I had the problem installing F15)

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