Closed osccto closed 11 months ago
That is an odd failure mode (one I've not seen before).
Could you list the contents of /run/user/0
?
In /run/user/0, I found:
$ sudo ls -lrt /run/user/0
total 0
-rw-r----- 1 root root 0 May 12 16:42 wayland-0.lock
drwx------ 2 root root 80 May 17 09:38 snap.ubuntu-frame-vnc
srwxr-xr-x 1 root root 0 May 17 09:38 wayland-0
drwx------ 4 root root 100 May 17 10:51 snap.our-electron
drwx------ 2 root root 80 May 22 08:08 snap.ubuntu-frame-osk
That looks normal. So I need to ask some more questions...
I assume your snap (our-electron
) and ubuntu-frame-osk
are connecting OK?
Could you also list the content of /run/user/0/snap.ubuntu-frame-vnc
?
Thanks
Note for anyone following up on this:
2023-05-17T09:38:10Z ubuntu-frame-vnc.daemon[22733]: ERROR: ../src/src/main.c: 384: WAYLAND_DISPLAY is not set in the environment 2023-05-17T09:38:10Z ubuntu-frame-vnc.daemon[22733]: ERROR: ../src/src/main.c: 1391: Failed to initialise wayland
These logs are output by wayvnc
after and because wl_display_connect(NULL)
fails. There is no indication logged why this failed (it isn't caused by WAYLAND_DISPLAY
not being set, that's just logged in case it is useful).
Closing for lack of activity.
I installed ubuntu-core on an intel system (amd64).
I then installed ubuntu-frame and ubuntu-frame-vnc. The ubuntu-frame was running fine (and displayed on the screen), but the ubuntu-frame-vnc not: