I moved my fvwm configuration to my new workstation and everything works wonderfully well, except…
My FvwmIconMan instance, that I use as an auto-hide task bar, displays bizarre colorset results when shown in the first of my two Xinerama screens. The screenshot below demonstrates the problem:
Note the FvwmIconMan at the bottom middle of the screen, that I have straddling my two Xinerama screens for effect. The colors on the right are correct… the colors are the left are messed up.
Can anyone shed some light on this behavior and how I might get around it? The relevant Colorsets and FvwmIconMan config (*TaskBar) is shown in the screenshot, but I can post more details, if necessary.
Using just XineramaSLS on a unified screen, because each Xinerama screen actually consists of two monitors from one of the two ports on a Quadro NVS 440 (quad mon card). So the video chips are all on the same card and should be the same.
Another observation, is that if I start an unconfigured FvwmIconMan from FvwmConsole, the colors are the same on both Xinerama screens. However, if I simply set a PlainColorset on a follow-up FvwmIconMan, it exhibits the bizarre behavior… as I drag it back and forth over the boundary, it smoothly changes the colors at that imaginary line. It’s fascinating, and I have no idea how to get a handle on it.
I also just tried the config on a dual-screen setup, using just the first two monitors, and thus bypassing Xinerama altogether. This time, the colors look fine on the same monitors that were problematic before… this would rule out hardware, no?
I have finally got xinerama working in my SiS 771/671 PCIE (avoid SiS graphic cards; see, for example, this thread). At the beginning I had exactly the same issue: wrong colors in one of the two screens. This is when my xorg.conf was written with two devices in mind. This was the initial structure:
Xinerama works wonderfully after adding these lines in my fvwm config:
XineramaPrimaryScreen 0
Xinerama on
Style * StartsOnScreen 0
In my case, wrong colors in xinerama was an issue related with xorg.conf. Hope it gives some ideas.