Michael D. Setzer II via users writes:
> On 24 Feb 2024 at 10:10, Sam Varshavchik wrote:
>
> > That's a no-go for me. My Fedora system is configured to automatically log
> > into a graphical desktop. This won't work for me, then.
>
> Not sure on the latest version of tigervnc on Fedora, for a while I
> was able to have it work, but had to change the configuration to
> have the vnc use XFCE (heard others had used mate or other) but
> the wayland/gnome 3 definitely do not allow for dual user sessions
> local/vnc.
Oh, this is a Gnome thing? That's not a problem for me, since I use XFCE
anyway.
But something is still broken. I went through the motions, set session=xfce,
but then something is still broken with systemd. systemctl start vncserver@:
1 results in:
Feb 24 11:30:33
monster.email-scan.com systemd[1]: Starting vncserver@:
1.service - Remote desktop service (VNC)…
Feb 24 11:30:34
monster.email-scan.com systemd[1]: Started vncserver@:
1.service - Remote desktop service (VNC).
Feb 24 11:30:35
monster.email-scan.com systemd[1]: vncserver@:1.service:
Deactivated successfully.
That's it, no further diagnostics, and nothing is listening on port 5901.
... 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.