Closed J4ckTh3R1pper closed 3 months ago
Looks like hyprland raises a protocol error when wayvnc tries to resize the headless output. This should not be a protocol error and this is the problem.
i switched to TightVNC client and it works fine now, strange
No, it isn't strange at all. TightVNC doesn't support client-side resizing, so it's not going to trigger this error.
No, it isn't strange at all. TightVNC doesn't support client-side resizing, so it's not going to trigger this error.
So what am I supposed to do to prevent TigerVNC from resizing the WM?
No, it isn't strange at all. TightVNC doesn't support client-side resizing, so it's not going to trigger this error.
So what am I supposed to do to prevent TigerVNC from resizing the WM?
This is a hyprland bug, not a TigerVNC bug or a wayvnc bug.
Client is TigerVNC, I got grey blank screen when connected to wayvnc
Useful information:
Please, try to gather as much of useful information as possible and follow these instructions:
Version:
Try to reproduce while capturing a trace log:
Describe how to reproduce the problem
WLR_BACKENDS=headless WLR_LIBINPUT_NO_DEVICES=1 Hyprland
wayvnc --log-level=debug 0.0.0.0