wayvnc black screen on raspberry pi connect

[george-ivanov]

After making the mistake of connecting hdm1 to a physical monitor AND running remote connect at the same time this error started happening whenever the physical monitor isn't connected and I only get a black screen when trying to connect remotely:

Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: *** BUG ***
Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: In pixman_region_union_rect: Invalid rectangle passed
Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: Set a breakpoint on '_pixman_log_error' to debug
Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: *** BUG ***
Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: In pixman_region_union_rect: Invalid rectangle passed
Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: Set a breakpoint on '_pixman_log_error' to debug
Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: wl_display#1: error 1: invalid arguments for zwlr_virtual_pointer_manager_v1#8.create_virtual_pointer_with_output
Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: ERROR: ../src/main.c: 507: Failed to dispatch pending
Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: *** BUG ***
Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: In pixman_region_init_rect: Invalid rectangle passed
Nov 22 21:44:57 raspberrypi rpi-connect-wayvnc[1218]: Set a breakpoint on '_pixman_log_error' to debug

Any ideas how to sort this out?

[any1]

I did fix some hotplugging issues in the latest release, which has not reached rpi repos yet, but it will soon.

In the meantime, you should be able to work around the problem by restarting the rpi-connect-wayvnc service: systemctl --user restart rpi-connect-wayvnc.

[george-ivanov]

Anything I can do to fix it?

[any1]

That depends on your skill level. You could try compiling labwc from source and running it, but there is an upgrade for that coming soon as well.

[george-ivanov]

Thanks! Will probably wait for the update then, unless I get really curious :-)

[Consolatis]

If you are using labwc, can you verify that you have a line like LABWC_FALLBACK_OUTPUT=NOOP-fallback in either ~/.config/labwc/environment or /etc/xdg/labwc/environment ? That should make labwc create a virtual output whenever the last physical output is gone.

You can also do a hotfix if you don't want to restart labwc by binding VirtualOutputAdd with an output name like NOOP-wayvnc to a keybind via ~/.config/labwc/rc.xml, labwc --reconfigure and then using that keybind. That will only keep the virtual output around for as long as labwc is running though.

[george-ivanov]

You're absolutely right! For some reason the environment file had gone missing. I compared it to the second Pi I've got running and copied the file across:

QT_WAYLAND_DISABLE_WINDOWDECORATION=1

DESKTOP_SESSION=LXDE-pi-labwc
WLR_XWAYLAND=/usr/bin/xwayland-xauth
XAUTHORITY=~/.Xauthority

XCURSOR_THEME=PiXflat
XCURSOR_SIZE=24

LABWC_FALLBACK_OUTPUT=NOOP-1

XKB_DEFAULT_MODEL=pc105
XKB_DEFAULT_LAYOUT=gb

Thanks both for your help!