Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] Inverted caps lock indicator #129

Open
lonix1 opened this issue Oct 14, 2024 · 4 comments
Open

[bug] Inverted caps lock indicator #129

lonix1 opened this issue Oct 14, 2024 · 4 comments

Comments

@lonix1
Copy link

lonix1 commented Oct 14, 2024

Sometimes when my laptop wakes from sleep, the caps lock indicator is inverted: it's off when caps is on, and on when caps is off.

Started after upgrading to ubuntu 24.04 (gnome 46.0).

I found two workarounds:

  • reboot
  • sometimes works: suspend again, then press capslock to wake
  • (since it uses wayland, I can't use the Alt-F2 r trick)

Any ideas?

@kazysmaster
Copy link
Owner

Try to disable-enable the extension. Otherwise it needs a fix that syncs it's state with the actual state of the keyboard when laptop resumes from suspend. I hope that there's a signal can be utilized.

@lonix1
Copy link
Author

lonix1 commented Oct 14, 2024

Thanks.

Try to disable-enable the extension

Tried that but unfortunately it doesn't help. Which is strange as one would expect it to read the current state of the keyboard.

syncs it's state with the actual state of the keyboard ... hope that there's a signal can be utilized

Yes that would be the ideal solution, assuming it's even possible.

@kazysmaster
Copy link
Owner

kazysmaster commented Oct 14, 2024

Tried that but unfortunately it doesn't help. Which is strange as one would expect it to read the current state of the keyboard.

If that's the case then the problem is in Clutter.get_default_backend().get_default_seat().get_keymap().get_caps_lock_state()
because the extension is getting it's state by calling this function when is enabled.

@lonix1
Copy link
Author

lonix1 commented Oct 14, 2024

Currently it's working, so I can only test the next time it breaks. I'll have to remember to update this thread with any observations I make.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants