https://bugs.freedesktop.org/show_bug.cgi?id=100760
--- Comment #3 from m...@advancedcontrols.com.au ---
Many thanks Ilia for those helpful suggestions.
The results of the experiments are, that in ZaphodHeads mode:
1. Running "DISPLAY=:0.1 gnome-terminal" under all window managers makes the
terminal display correctly, but on display :0.0.
2. Running "DISPLAY=:0.1 mate-terminal" or "DISPLAY=:0.1 xterm" under Gnome 3,
Gnome Classic, or Gnome on X (rather than Wayland) makes the terminal appear on
display :0.1 without flickering, but there's no window border, and any typing
goes to the original terminal.
3. Running "DISPLAY=:0.1 mate-terminal" or "DISPLAY=:0.1 xterm" under MATE
causes the same as above plus the intense flickering.
So the flickering is a MATE problem, but the inability to use the second
display is an X problem. This matches my experience with the problems starting
under the proprietary driver, with the background image and menus going first,
and later requiring the explicit setting of DISPLAY.
I've found independent virtual desktops such a productive feature, I'm
disappointed it's going away.
I suppose other than the fix-it-myself option you suggest, I could:
1. Try to install an X (and maybe also a MATE) downgrade, such as the one that
was working on F23,
2. Get a new graphics card to see whether that works with twin X-displays on
either Nouveau or the proprietary driver (again the hardware will have
outlasted the software). Is anyone successfully using Zaphod on a current
distro?, or
3. Wait for an X update that fixes this.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
