compiz team mailing list archive

[Adrian Wilkins <adrian.wilkins@xxxxxxxxx>]

Noticed this again recently because the "primary" screen appears to have
switched between driver versions.

Despite what's said above, on my hardware the driver seems to pick the
screen it syncs to and does not respect the "primary" setting for this
purpose.

Previously this meant that I had flipped my monitor cables around (and
flipped the screen config around in Windows) so that the synced display
was my primary display and the tearing was on the secondary. Now the
sync has shifted to the other display so I guess I'll be flipping my
cables around again.

This is most noticeable when playing video as one does not drag screens
around constantly. I have a feeling that in many cases bugs like #151674
are probably also attributable to this fault.

Isn't this down to some awful kludge in X that identifies displays by a
concatenation of their resolution and refresh rate - the end result
being that you can't have two displays with identical resolutions and
refresh rates because that would mean X couldn't tell them apart? It
would seem to be worth checking this rumour out but I don't have the
time or grok C and X well enough.

-- 
Uses single refreshrate for separate X screens
https://bugs.launchpad.net/bugs/201342
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in ubuntu.