Samuel Sieb writes:
On 2/24/24 08:52, Sam Varshavchik wrote:
> Sam Varshavchik writes:
>> 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.
It's an X limitation or an operating system limitation if you really want to
call it that. There can only be one X server on a port. Change the display
number.
They are different ports. I just verified that DISPLAY in the VNC session
is :1.0
On the system console it's :0.0, of course.
Yet, I cannot start both of them, on Fedora, if both are running xfce. This
is a documented limitation, in the package's HOWTO.
I run a VNC server with openbox using systemd and it works fine.
Now, try getting your VNC server up with an existing graphical session
already running. It won't work, if both are XFCE (or if both are gnome, as I
understand it).