On 16/01/2025 00:38, Tim Woodall wrote:
I don't think you understand my setup. Remote XDMCP thin client.
I have not checked current state of affairs. I believed that it was
working greet 20 years ago before hardware graphics acceleration and
client-side font rendering. That is why I mentioned VNC and RDP.
But there are two window managers, because there are two logins and the
different $DISPLAY are different physical monitors on different physical
hdmi driver hardware (the remote one is an rpi)
I expect troubles from 2 GUI logins for the same user. I am afraid that
many user D-Bus services are not ready to have multiple instances. At
least some efforts are required to isolate D-Bus sessions. I expect that
2 different users will be safer.
When you did your ssh test, the machine you ssh to was already running
chrome with a different $DISPLAY?
Sure
That's interesting because I would
have expected that to do similar to what I'm seeing and suggests that it
can be made to work. Everything else I've tried works as I expect.
I strongly suggest to create temporary profiles for experiments.
chromium --user-data-dir="$HOME/profileA"
chromium --user-data-dir="$HOME/profileB"
Actually for tests I had additional --password-store=basic, but for
regular sessions with logins to various sites you almost certainly use
SecretsService exposed through D-Bus.
The same for Firefox (unsure if --class is really necessary, I have
impression that earlier it affected what control socket Firefox used).
firefox-esr --class FirefoxA --profile ~/ff-a
firefox-esr --class FirefoxB --profile ~/ff-b
