Bug 8527 - Caps lock/Num lock synchronisation unreliable on GNOME Wayland
Summary: Caps lock/Num lock synchronisation unreliable on GNOME Wayland
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Desktop environment (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-24 14:17 CET by Adam Halim
Modified: 2025-02-25 13:34 CET (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Minimal example to trigger issue (1.12 KB, text/x-csrc)
2025-02-24 16:05 CET, Adam Halim 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Adam Halim cendio 2025-02-24 14:17:14 CET 
Broken out from bug 7985.

Looks like there's an issue on GNOME Wayland:

1. Connect to a session
2. Switch to a different window locally
3. Switch lock state (e.g. enable caps lock)
4. Switch focus back to the client
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 client
8. Lock state is now synced

You have to switch focus twice before lock states get synced. This should happen immediately.

I could not see this issue on GNOME X11, KDE, MATE, or on Windows/Mac.
Comment 1 Adam Halim cendio 2025-02-24 15:01:07 CET 
I've reported this to RedHat:

https://bugzilla.redhat.com/show_bug.cgi?id=2347305
Comment 2 Adam Halim cendio 2025-02-24 16:05:28 CET 
Created attachment 1264 [details]
Minimal example to trigger issue

I managed to get a minimal working example using only X11, and RedHat referred me to mutter instead:

https://gitlab.gnome.org/GNOME/mutter/-/issues/3929
Note You need to log in before you can comment on or make changes to this bug.