Bug 503690 - Overlapping region on multihead configuration
Overlapping region on multihead configuration
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-06-02 04:34 EDT by Vitaly Mayatskikh
Modified: 2018-04-11 04:56 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 08:47:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/Xorg.0.log (79.49 KB, text/plain)
2009-06-05 05:50 EDT, Vitaly Mayatskikh
no flags Details
/etc/X11/xorg.conf (1.58 KB, text/plain)
2009-06-05 05:51 EDT, Vitaly Mayatskikh
no flags Details
right side of LVDS (left monitor) (863.54 KB, image/jpeg)
2009-06-05 05:52 EDT, Vitaly Mayatskikh
no flags Details
Left side of TMDS-1 (right monitor) (802.14 KB, image/jpeg)
2009-06-05 05:53 EDT, Vitaly Mayatskikh
no flags Details
Right side of TMDS-1 (right monitor) (576.03 KB, image/jpeg)
2009-06-05 05:53 EDT, Vitaly Mayatskikh
no flags Details

  None (edit)
Description Vitaly Mayatskikh 2009-06-02 04:34:25 EDT
On system with 2 displays (for example, LVDS and TMDS-1) run these commands:

$ xrandr --output TMDS-1 --right-of LVDS
$ xrandr --output TMDS-1 --rotate left

And in the left side of TMDS-1 you will see 1 column from the right side of LVDS. Right column of TMDS-1 is not visible. Seems like a wrong calculation of regions positions somewhere in xinerama (?) extension. Bug does not appear if orientation of TMDS-1 is normal.

I have Lenovo T61 laptop with X3100 video adapter and Fedora rawhide (pre-11).
Comment 1 Matěj Cepl 2009-06-04 19:03:16 EDT
Hi, Vitaly,

could we get /var/log/{dmesg,Xorg.0.log,messages} and /etc/X11/xorg.conf (if any) attached here as separate uncompressed attachments please? Could you also try to make a photograph or something of the issue, please?

Thank you very much
Comment 2 Vitaly Mayatskikh 2009-06-05 05:50:59 EDT
Created attachment 346624 [details]
Comment 3 Vitaly Mayatskikh 2009-06-05 05:51:26 EDT
Created attachment 346625 [details]
Comment 4 Vitaly Mayatskikh 2009-06-05 05:52:40 EDT
Created attachment 346626 [details]
right side of LVDS (left monitor)
Comment 5 Vitaly Mayatskikh 2009-06-05 05:53:14 EDT
Created attachment 346627 [details]
Left side of TMDS-1 (right monitor)
Comment 6 Vitaly Mayatskikh 2009-06-05 05:53:41 EDT
Created attachment 346628 [details]
Right side of TMDS-1 (right monitor)
Comment 7 Bug Zapper 2009-06-09 12:57:51 EDT
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:
Comment 9 Matěj Cepl 2009-11-05 13:30:24 EST
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Comment 10 Vitaly Mayatskikh 2009-11-09 05:18:31 EST
Problem still exists. I'm running latest Fedora rawhide (F-12).
Comment 11 Bug Zapper 2010-04-27 10:37:14 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 13 Bug Zapper 2010-06-28 08:47:14 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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