Failed to listen on socket or bind to its address

I can't seem to run wayvnc, kill it, and then run it again unless I pick a new port or reboot the computer. ### Useful information: - **Version:** - wayvnc: 0.9.1 - neatvnc: 0.9.5 - aml: 0.3.0 Using Raspberry Pi OS bookworm ARM64 wayland labwc. Kernel version 6.12.47+rpt-rpi-v8, not using a config file, no vnc client is being used. Run this command **twice**: `rm -f /tmp/auto_vnc.sock /tmp/auto_ctl.sock && wayvnc --unix-socket=/tmp/auto_vnc.sock --socket=/tmp/auto_ctl.sock -p 5945 127.0.0.1` ``` pi@raspberrypi:~ $ rm -f /tmp/auto_vnc.sock /tmp/auto_ctl.sock && wayvnc --unix-socket=/tmp/auto_vnc.sock --socket=/tmp/auto_ctl.sock -Ldebug -p 5946 127.0.0.1 Info: Capturing output HDMI-A-2 Info: >> Northgate Computer Systems NCS HDMI (HDMI-A-2) 1920x1080+0x0 Power:UNKNOWN DEBUG: ../src/ctl-server.c: 809: Initializing wayvncctl socket: /tmp/auto_ctl.sock Info: Listening for connections on 5946 ^C pi@raspberrypi:~ $ rm -f /tmp/auto_vnc.sock /tmp/auto_ctl.sock && wayvnc --unix-socket=/tmp/auto_vnc.sock --socket=/tmp/auto_ctl.sock -Ldebug -p 5946 127.0.0.1 Info: Capturing output HDMI-A-2 Info: >> Northgate Computer Systems NCS HDMI (HDMI-A-2) 1920x1080+0x0 Power:UNKNOWN DEBUG: ../src/ctl-server.c: 809: Initializing wayvncctl socket: /tmp/auto_ctl.sock ERROR: ../src/main.c: 918: Failed to listen on socket or bind to its address. Add -Ldebug to the argument list for more info. DEBUG: ../src/ctl-server.c: 941: Enqueueing detached event: {} DEBUG: ../src/ctl-server.c: 968: Enqueued detached event for 0 clients ``` As mentioned earlier, if I change `5946` to a different number, it works once more, but not on repeat runs. This made me think that port was staying reserved by a zombie process, but I verified after Ctrl+C there are no wayvnc processes, and `sudo ss -tulpn | grep 5946` returned no results. As I'm using socket files, I would prefer if wayvnc did not try to open a port at all. But when I try not specifying a port, it results in the same issue, making me think wayvnc is still trying to reserve a default port on localhost. ``` $ rm -f /tmp/auto_vnc.sock /tmp/auto_ctl.sock && wayvnc --unix-socket=/tmp/auto_vnc.sock --socket=/tmp/auto_ctl.sock -Ldebug Info: Capturing output HDMI-A-2 Info: >> Northgate Computer Systems NCS HDMI (HDMI-A-2) 1920x1080+0x0 Power:UNKNOWN DEBUG: ../src/ctl-server.c: 809: Initializing wayvncctl socket: /tmp/auto_ctl.sock ERROR: ../src/main.c: 918: Failed to listen on socket or bind to its address. Add -Ldebug to the argument list for more info. DEBUG: ../src/ctl-server.c: 941: Enqueueing detached event: {} DEBUG: ../src/ctl-server.c: 968: Enqueued detached event for 0 clients ``` Is this a known issue? Am I using wayvnc incorrectly here, or do most users never have the need to restart a wayvnc server?