which is to say, the new version of xinerama is reporting that there are two screens that OVERLAP. Which
is, in a word, bullshit.
Someone has suggested that perhaps this has something to do with
XRRGetOutputInfo()->connection
but that is, as far as I can tell,
1) a brand new interface, and
2) completely, utterly undocumented.
So, as long as XRANDR continues to be an undocumented, experimental moving target, I have not the first
clue what to do to work around this latest braindamage.
Bug reports without verbose logs are usually useless.
But in this case, based on what was in another report, I think I can predict that the verbose log will say
something like
xscreensaver: 13:27:37: Xinerama layout:
xscreensaver: 13:27:37: + 0/0: 1600x1200+0+0
xscreensaver: 13:27:37: 1/0: 1360x768+0+0
which is to say, the new version of xinerama is reporting that there are two screens that OVERLAP. Which
is, in a word, bullshit.
Someone has suggested that perhaps this has something to do with o()->connection
XRRGetOutputInf
but that is, as far as I can tell,
1) a brand new interface, and
2) completely, utterly undocumented.
So, as long as XRANDR continues to be an undocumented, experimental moving target, I have not the first
clue what to do to work around this latest braindamage.