Bug 746794 - Dual Head: left screen shown on right monitor and left monitor shows black
Summary: Dual Head: left screen shown on right monitor and left monitor shows black
Keywords:
Status: CLOSED DUPLICATE of bug 725219
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-17 19:34 UTC by Dr. Tilmann Bubeck
Modified: 2011-10-25 14:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-25 14:24:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dr. Tilmann Bubeck 2011-10-17 19:34:14 UTC
Description of problem:
I have a correct dual head configuration which is correctly detected by anaconda/xorg. When I move the mouse onto the right screen directly after the start of anaconda/xorg, then this right screen shows the contents which is normally shown on the left screen. The left screen is black, but could be entered with the mouse (cursor shown) and it is correctly configured on the left side.

The problem is, that the "Next" Button is then drawn even far more right, outside the screen. It is therefore invisible and not clickable.

The problem does not happen, if I do not move the mouse or move it to the left screen.

Version-Release number of selected component (if applicable):
anaconda in fc16-beta

How reproducible:
Every time

Steps to Reproduce:
1. Boot FC16 on dual head
2. Move mouse cursor to the right screen, immediately after xorg start
3.
  
Actual results:
left contents of right screen, right contents nowhere, left screen black.

Expected results:
left contents of left screen, right contents on right screen


Additional info:

Comment 1 Chris Lumens 2011-10-25 14:24:19 UTC

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


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