Fedora Account System
Red Hat Associate
Red Hat Customer
CapsLock/NumLock states are supposed to synchronize when using vncviewer, i.e. if a lock state is changed outside the session (locally), focusing on vncviewer should sync the state immediately to the server. With vncviewer on GNOME Wayland, the sync states are synced the second time vncviewer gets focused, instead of immediately with the first focus. I was unable to see this issue GNOME X11, MATE, or KDE Wayland. Reproducible: Always Steps to Reproduce: 1. Connect to a server 2. Switch to a different window locally 3. Switch lock state (e.g. enable caps lock) 4. Switch focus back to vncviewer 5. Lock state is not synced (I see fake key events with xev). 6. Switch to a different window locally 7. Switch focus back to vncviewer 8. Lock state is now synced I could reproduce this with Xvnc sessions running GNOME and KDE.
Hi, I see your upstream https://bugzilla.cendio.com/show_bug.cgi?id=8527 issue. I'm just not sure why this has been reported to Tigervnc. If you think it's a GNOME Wayland specific issue, it should be most likely reported to Mutter, but you better to report an upstream issue and not a Fedora one.
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
Hi, my bad! I've created an issue with GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/3929. Thanks!