looking into this further it turns out this doesn't appear to be related to the network namespace setup. i got rid of the network namespace and the same issue occurs:
1. running the wayvnc service works. i can connect with tigervnc from another machine with no issues.
2. stopping the wayvnc service and running sudo /usr/sbin/wayvnc-run.sh directly starts wayvnc, and allows connections, but the vnc client only displays a grey screen.
3. trying sudo waynvcctl -S /tmp/wayvncctl -S /tmp/wayvnc/wayvncctl.sock attach wayland-1 returns:
ERROR: Failed to execute command: attach: Failed to connect to WAYLAND_DISPLAY="wayland-1"
Ensure wayland is running with that display name
4. trying sudo waynvcctl -S /tmp/wayvncctl -S /tmp/wayvnc/wayvncctl.sock output-list causes a segmentation fault.
thanks again
1. running the wayvnc service works. i can connect with tigervnc from another machine with no issues.
2. stopping the wayvnc service and running sudo /usr/sbin/wayvnc-run.sh directly starts wayvnc, and allows connections, but the vnc client only displays a grey screen.
3. trying sudo waynvcctl -S /tmp/wayvncctl -S /tmp/wayvnc/wayvncctl.sock attach wayland-1 returns:
ERROR: Failed to execute command: attach: Failed to connect to WAYLAND_DISPLAY="wayland-1"
Ensure wayland is running with that display name
4. trying sudo waynvcctl -S /tmp/wayvncctl -S /tmp/wayvnc/wayvncctl.sock output-list causes a segmentation fault.
thanks again
Statistics: Posted by 0nobody0 — Thu Aug 01, 2024 7:33 pm