Additional reproduction detail: the failure occurs only on the FIRST client connection after wayvnc starts.
Before any client has connected, wayvnc/neatvnc has not captured a frame yet, so ServerInit advertises a 1280x720 placeholder framebuffer and the server must then send an ExtendedDesktopSize resize to the real output size (here 1920x1200). That resize is the one libvncclient discards because the screen id is 0, and the following full-frame update fails with "Rect too large". Once any client has triggered a capture (a working viewer such as TigerVNC, or even a failed libvncclient attempt), wayvnc keeps the real size, later connections receive 1920x1200 directly in ServerInit, no resize is needed, and Remmina connects fine. So to reproduce reliably: restart wayvnc (systemctl restart wayvnc on Raspberry Pi OS), then connect with Remmina as the first client. A second Remmina connection without restarting wayvnc will succeed and does not demonstrate the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2166587 Title: libvncclient rejects ExtendedDesktopSize resize when screen id is 0 (wayvnc/neatvnc) → "Rect too large", connection dropped — fixed upstream in PR #620, please cherry-pick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvncserver/+bug/2166587/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
