Re: tigervnc server configuration limitation
On 2/24/24 08:52, Sam Varshavchik wrote:
... and that was because even xfce is not going to work. The reason
was
dumped into ~/.vnc/*log:
/usr/bin/startxfce4: X server already running on display :1
MESA: error: ZINK: failed to choose pdev
glx: failed to create drisw screen
failed to load driver: zink
xfce4-session-Message: 11:40:42.960: SSH authentication agent is already
running
xinit: connection to X server lost
So this is not a Gnome limitation, but a systemd limitation.
You say the reason is there, but what reason are you seeing? The only
difference from when it does work is that last line from xinit.
(I was mistaken about the "already running" message. That should happen
because Xvnc is started and xfce should not be starting an X server.)
It does have something to do with running from systemd, but I have no
idea what it is. The xfce session starts, but something fails. If you
run the same command directly, it starts up correctly.