Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#62758 - Keyboard layout LED stays on after first toggle
Attached to Project:
Arch Linux
Opened by Paulo Fino (burafino) - Monday, 27 May 2019, 16:34 GMT
Last edited by freswa (frederik) - Saturday, 22 February 2020, 22:05 GMT
Opened by Paulo Fino (burafino) - Monday, 27 May 2019, 16:34 GMT
Last edited by freswa (frederik) - Saturday, 22 February 2020, 22:05 GMT
|
DetailsWhen using two different keyboard layouts (English and Russian in my case) and setting xkb-options to use a keyboard LED to indicate the alternative layout ('grp_led:caps' in my case), in Gnome on Wayland session the LED turns on after the first time I toggle the layout, nad then stays on, no matter how many times or in which way I switch layouts. It's supposed to turn on on switching to Russian and then turn off on switching back to English. In Gnome on Xorg session, the LED works correctly, turning off when I switch back to the main layout.
Steps to reproduce: 1. Add a second keyboard language/layout 2. Add 'grp_led:caps' or 'grp_led:scroll' to /org/gnome/desktop/input-sources/xkb-options in dconf editor 3. Switch layouts, the respective LED turns on 4. Switch layouts again, the LED stays on under Wayland, but turns off under Xorg |
This task depends upon
Closed by freswa (frederik)
Saturday, 22 February 2020, 22:05 GMT
Reason for closing: None
Additional comments about closing: This seems pretty stalled to me. If it's still an issue, please fill a re-open request. Thank you :)
Saturday, 22 February 2020, 22:05 GMT
Reason for closing: None
Additional comments about closing: This seems pretty stalled to me. If it's still an issue, please fill a re-open request. Thank you :)