On Tue, 14 Jan 2025, Max Nikulin wrote:
On 14/01/2025 16:32, Tim Woodall wrote:
On Tue, 14 Jan 2025, Max Nikulin wrote:
On 14/01/2025 04:40, Tim Woodall wrote:
On Mon, 13 Jan 2025, Daniel Harris wrote:
I am a very long time happy firefox user using debian stable, but what
on
earth is going on with firefox lately. It is terrible. So slow and why
is
it not possible to have 2 separate instances anymore.
It's not possible with chromium either. I have two separate X servers
running on two separate machines but displaying a desktop from a single
machine (two window managers running)
Tim, likely you are confusing ability of the same browser instance to have
windows on multiple DISPLAYs and running multiple instances on the same
display.
I don't think so. I want to run multiple instances on different
displays. But any attempt to do anything on the second display seems to
have chrome first looking for the existing instance and then displaying
everything on that display.
I am still in doubts if Daniel needs different DISPLAYs.
Out of curiosity I have tried another instances of Chromium and Firefox from
"ssh -X". Perhaps Firefox relies too much on hardware graphics acceleration
and menus were not rendered. Chromium worked a bit better, but e.g. open file
dialog appeared on the local screen. It is more or less expected. Desktop
portal was running on the local display and I was not tried to isolate D-Bus
session. I consider it as a limitation of desktop user session rather than of
browsers.
I have not tried it, but sharing whole session might work better, e.g. RDP
and gnome-remote-desktop. It seems
<https://help.gnome.org/users/gnome-help/stable/sharing-desktop.html.en>
describes VNC access.
I don't think you understand my setup. Remote XDMCP thin client.
Everything for the two displays, except the actual X server, is running
on the same machine.
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 suspect you can recreate this by running an X session on vt8 too. If
you login and start chrome on vt7 you won't be able to start it on vt8
too. (I haven't actually tried this)
There might be a way to do it, but everything I tried that starts
chromium on display fd01:8b0:bfcd:300:dea6:32ff:fe84:c103:0.0 creates
windows on display :0.0 (assuming chrome is already running there).
When you did your ssh test, the machine you ssh to was already running
chrome with a different $DISPLAY? 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.
