Zaphod displays...the indispensable config no one knows about

I've done it for years and years but only recently learned it's call "zaphod": two or more independent X displays running connected to the same machine, but each display being its own X11 environment. Nvidia has well supported this for many years and I use NVidia GPUs so works for me.

However, what doesn't work well, is desktop/window-manager support for such configurations. Most of the "presently supported" environments seem broken by design when when you try to fire up multiple instances of them: one for each X11 display. Sure, we can take a WAG and arrive at the conclusion that most of the devs have either never heard of zaphod or don't think it's a wide enough following to thoroughly test in that environment...but I digress because really, what FOSS projects do any real internal testing? Isn't that what the users are for? LOL

My latest nemesis is taskbars...I graduated from fvwm a few years ago to openbox...works well for my needs. The typical taskbar for openbox is tint2. It does seem to work for zaphod but is kind of fragile and can easily spin massive warnings into the X11 logfile. The configuration utility is buggy and can crash or generate improper config files. So I went on a quest for a different taskbar app...None of the web-search found apps work for zaphod: either by not storing individual profiles for each display, nor allowing multiple instances of the taskbar app to run concurrently.

Anyway, I needed to vent...Anyone have suggestions for well working zaphod compatible taskbars?
 
Never tried 2 Xorg servers 1 computer but with a root window overlapping 2 displays, I comfigured openbox to start different programs always on the same monitor depending on the executable name. It also supports keyboard shortcuts to move programs to or from the other side.
I have no idea how to tell a program it has to run on 1 of 2 X-servers. Does this situation also have 2 independent mouse pointers?
 
I used Zaphod mode until recently. With fvwm2.

Things can be confusing since there is only one window manager for both displays.
 
I used Zaphod mode until recently. With fvwm2.

Things can be confusing since there is only one window manager for both displays.
Actually under openbox there are two distinct instances of the window manager: one for each display. That makes me feel good. LOL Same with tin2 taskbar: an instance for each display.
 
Actually under openbox there are two distinct instances of the window manager: one for each display. That makes me feel good. LOL Same with tin2 taskbar: an instance for each display.
Just tried that on a dual screen system: A window manager is already running on screen 0.
So this needs a special xorg.conf with 2 screen sections?
 
Back
Top