5

Caps Lock seems to reset to ON every time I resume my laptop (Ubuntu 24.10 fully updated with GNOME) from suspend, and it is ON separately for each application. For instance, when I wake the laptop:

  1. I try to log in with my password, but it fails, then I notice the "Caps lock is on" message, even though the Caps Lock indicator on my keyboard is off. I hit the Caps Lock key, the indicator turns on, but I'm able to type my password and log in.
  2. I hit the Super key and type the name of an application, but Caps Lock is on again. I hit the Caps Lock key, the indicator turns off, and resume typing the name of the application.
  3. I open a terminal and start typing CD ~/dOCU...; I hit Caps Lock again, the light turns on, and... you get the idea.

I don't see others mentioning this issue here or on https://gitlab.gnome.org, so I expect it might be a local problem, but I can't figure out what.

  1. Nothing is selected in GNOME Tweaks → Keyboard → Additional Layout Options.
  2. In the standard Keyboard settings, my input method is English (US), I selected Use the same source for all windows, and I haven't changed any settings for Special Character Entry.

Anything else I can check?

BeastOfCaerbannog
  • 16,936
goodmami
  • 153

1 Answers1

5

It seems that you are experiencing this bug: Caps lock confused after suspend and resume

According to Daniel van Vugt's comment, this bug is also reported several times in GNOME's GitLab:

There is a workaround suggested by Janne Snabb (which requires Tweaks: sudo apt install gnome-tweaks) and confirmed by two other users that I'm quoting below (with some formatting added by me):

This workaround has saved my sanity:

  1. Go to GNOME Tweaks → Keyboard → Additional Layout Options → Compatibility options
  2. Enable Both shifts together enable Caps Lock; one Shift key disables it

Here is a screenshot of the relevant option:

Screenshot showing the option mentioned above

BeastOfCaerbannog
  • 16,936
  • 1
    Thank you, somehow my search terms missed those bug tickets. Similar to others on those tickets, a full reboot seems to have resolved the issue, for now. But it seems this bug is several years old, so the workaround will certainly be useful. (I also appreciate your formatting edits to the original post!) – goodmami Apr 22 '25 at 16:16
  • @goodmami You're welcome! I'm glad that you found this answer helpful! :) – BeastOfCaerbannog Apr 22 '25 at 18:25