Re: sys-gui-vnc non-working in Qubes 4.2-RC4
sys-gui-vnc appears to be non-working in Qubes 4.2-RC4 with fully updated dom0 and fedora-38-xfce template.
Started fresh 2 times, being very careful with exact steps, and the same bugs/problems occur each time.
Using sys-remote qube to access sys-gui-vnc via VNC, but VNC connection is always dropped and closed automatically with no connection.
Confirmed that qubes.ConnectTCP traffic is allowed through from sys-remote to sys-gui-vnc, but x11vnc server does not appear to be running in sys-gui-vnc.
Maybe this 4.2 sys-gui-vnc breakage can be confirmed or troubleshot here to make it work?
#1 These dom0 commands seem to succeed fine:
sudo qubesctl top.enable qvm.sys-gui-vnc
sudo qubesctl top.enable qvm.sys-gui-vnc pillar=True
sudo qubesctl --all state.highstate
sudo qubesctl top.disable qvm.sys-gui-vnc
qubes-prefs default_guivm sys-gui-vnc
qvm-shutdown --all --wait
echo "qubes.ConnectTCP * sys-remote @default allow target=sys-gui-vnc" >> /etc/qubes/policy.d/30-user-networking.policy
Confirmed sys-gui-vnc services on:
qvm-service --list sys-gui-vnc
#2 For sys-remote, I’ve tried using fedora-38-xfce & debian-12-xfce with multiple various VNC viewer applications, without success:
The VNC viewer applications never connect and always instantly throw connection drop errors, like:
"The connection was dropped by the server before the session could be established."
Confirmed qubes.ConnectTCP: If I remove the /etc/qubes/policy.d/30-user-networking.policy file, then when attempting to connect the VNC app, a Dom0 notification in the upper right corner says:
"Denied qubes.ConnectTCP+5900 from sys-remote to @default"
so this suggests to me that with this policy file enabled my VNC port 5900 traffic is being successfully routed to the sys-gui-vnc qube.
Really needing to get this sys-gui-vnc feature working, so happy to provide any diagnostics needed to help further troubleshoot.
Anyone know how to get sys-gui-vnc working?