STEPS TO REPRODUCE 1. Add 'Lock Keys Status' widget to the system tray 2. Configure Caps Lock key to switch layouts (via localectl or systemsettings) 3. Switch to a different layout using Caps Lock key OBSERVED RESULT 'Lock Key Status' tray icon shows that Caps Lock is activated, but actually it isn't EXPECTED RESULT 'Lock Keys Status' tray icon doesn't show that Caps Lock is activated SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.6-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 14,5 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: LENOVO Product Name: 20Y7003TRT System Version: ThinkPad E14 Gen 3 ADDITIONAL INFORMATION Used to work properly about 3 weeks ago. Presumably KDE update broke something.
Hello, I'm confuse with the request. Why would you want to use the standard Caps Lock key the switch the keyboard layout? Are you not using it when writing text? I feel like this is very personal usage of Caps Lock key and the widget is working as expected. Regards
> Why would you want to use the standard Caps Lock key the switch the keyboard layout? It is a well-placed single button layout switch. When using layouts in different languages one has to often switch between them, e.g. programming in English, talking to colleagues in another language. > Are you not using it when writing text? Writing something in all caps is much more rare occasion, than switching layouts in a multi-language setup. I use Shift+Caps when I need the original Caps Lock function. This configuration is not that uncommon, e.g. ArchWiki suggests it as the default method to switch layouts: https://wiki.archlinux.org/title/Xorg/Keyboard_configuration#Switching_between_keyboard_layouts Anyway, putting all personal preferences aside XKB (grp:caps_toggle) and KDE (systemsettings) support this configuration, so it is expected to be supported by Plasma properly.
ok, thanks for explanation. Lets see if we have some inputs from developers. Regards
Can you specify *exactly* how you set the caps lock key up to switch layouts? I ask because I have used the Advanced tab of the Keyboard page to use my caps lock key to be the Compose key, and when doing it this way, it no longer functions as a caps lock key at all and thus doesn't trigger the widget's detection. This is probably the kind thing you want to do as well.
(In reply to Nate Graham from comment #4) > Can you specify *exactly* how you set the caps lock key up to switch layouts? > > I ask because I have used the Advanced tab of the Keyboard page to use my > caps lock key to be the Compose key, and when doing it this way, it no > longer functions as a caps lock key at all and thus doesn't trigger the > widget's detection. This is probably the kind thing you want to do as well. # localectl --no-convert set-x11-keymap us,ru pc104 '' grp:caps_toggle,grp_led:caps # systemctl reboot The problem persists if after this I additionally configure Caps Lock key as the main layout switching shortcut in systemsettings -> Input Devices -> Keyboard -> Layouts.
Thanks. I cannot reproduce the problem on Fedora 36 with the Wayland session. Does it also happen if you make your caps lock get into your compose key (rather than being the layout switching key) using the Keyboard Layouts page in System Settings
Same here: Fedora 36 with Wayland session. Could you please provide a more specific way to toggle the option you've mentioned? I'm not familiar with compose keys.
System Settings > Input Devices > Keyboard > "Advanced" tab > Position of Compose key > Caps Lock
(In reply to Nate Graham from comment #8) > System Settings > Input Devices > Keyboard > "Advanced" tab > Position of > Compose key > Caps Lock Enabling this option prevents me from using Caps Lock as the layout switch key. Caps Lock now doesn't seem to have any effect at all.
Yes, you can only use the caps lock key for one thing at a time with the options on that page. In terms of effect, focus a text field, press the Caps Lock key, and press the "u" key twice. You should see it type "ŭ". If it does that, then you have successfully set the Caps Lock key as your Compose key. In this state, does pressing it trigger the Lock Keys Status plasmoid?
(In reply to Nate Graham from comment #10) > Yes, you can only use the caps lock key for one thing at a time with the > options on that page. > > In terms of effect, focus a text field, press the Caps Lock key, and press > the "u" key twice. You should see it type "ŭ". If it does that, then you > have successfully set the Caps Lock key as your Compose key. In this state, > does pressing it trigger the Lock Keys Status plasmoid? Yes, if I press "u" key twice, I can see "ŭ" in the input field. In this state plasmoid is not triggered.
Ok, great. Now, in that same table view, unset Caps Lock as your Compose key, and check the checkbox by "Switching To Another Layout > Caps Lock". Now, when you press Caps Lock, does the Lock Keys Plasmoid get triggered?
(In reply to Nate Graham from comment #12) > Ok, great. Now, in that same table view, unset Caps Lock as your Compose > key, and check the checkbox by "Switching To Another Layout > Caps Lock". > > Now, when you press Caps Lock, does the Lock Keys Plasmoid get triggered? No, it isn't triggered this way. I've done a bit more experimenting. If I enable "Switching To Another Layout -> Caps Lock" AND "Use keyboard LED to show alternative layout -> Caps Lock", then the plasmoid triggers on layout switches. In kxkbrc I see the same options as in my localectl config: "grp:caps_toggle,grp_led:caps".
It would appear that "Use keyboard LED to show alternative layout -> Caps Lock" is the culprit here. Can confirm that.
Same here with Plasma 6.1.1
Same here with Plasma 6.2.1.
Please don't change version numbers or report that something is still a problem. If the bug report is open, it's safe to assume it's still a problem.
(In reply to Nate Graham from comment #17) > Please don't change version numbers or report that something is still a > problem. If the bug report is open, it's safe to assume it's still a problem. Ok