Not sure this is the right component, but I'm running xorg-x11-server-Xwayland-23.2.4-1.fc39.x86_64. I'm not sure how my machine got into this state, but I'm experiencing inconsistent caps lock behavior. When unlocking the screen, I need to have the light on the button OFF to type my password. For Firefox, Emacs, and Terminal windows, I need to have the caps lock light ON to type lowercase normally. Then when Emacs was opening an encrypted file, when it greyed out the screen and gave me a window to input the decryption key, I needed to have the light OFF again. I've never seen this behavior before this week. Let me know what would be helpful to diagnose it.
I'm also seeing this behavior, running wayland/gnome. What appears to be is that apps have the opposite state of the caps lock led indicator, and gnome-shell, lockscreen, activities display (mutter?) have the correct state. I don't see this on a fresh bootup. It seems to happen most when I suspend/resume my laptop a few times. I see this across multiple laptops, and it started after the upgrade to fedora 39. This does not seem related to xwayland, as whether I run xterm or gnome-terminal, the case matches. It seems more of a disparity between gnome-shell and apps.
I had to reboot to install system updates, and likewise for me that clears up the problem. But after a few weeks and wake/sleep cycles, it's happening again for me right now. So if there's any diagnostics I can run, let me know. (And even if I have to reboot again, apparently this happens often enough it'll probably re-occur and I can run any diagnostics then, if you leave instructions.) Changing the component in case Wade is right that's where the problem is. FTR, I'm currently running gnome-shell-45.4-1.fc39.x86_64.
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!
Not sure gnome-shell is responsible, but reported at: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7464
Upstream bug moved to: https://gitlab.gnome.org/GNOME/mutter/-/issues/3340