SUMMARY In a fresh Kubuntu 23.04 install, I have set the compose key to be on CapsLock. After every login, I have to open the Keyboard Advanced properties to set it again. Actually the settings display the correct state, but they aren't in effect. What Is needed to make them effective again is to reapply them. Since the "Apply" button is deactivated, one must tick any of the boxes in the advanced section of the keyboard properties so that the Apply button is enabled. Then this setting can be applied. Continuing I then untick that option again and Apply again to return to the state I actually wanted. This is my kxbrc file for what it's worth: [$Version] update_info=kxkb.upd:remove-empty-lists,kxkb.upd:add-back-resetoptions,kxkb_variants.upd:split-variants [Layout] DisplayNames=, LayoutList=de,kr Model=dell Options=grp:alt_space_toggle,compose:caps,caps:none,eurosign:e,shift:both_capslock ResetOldOptions=true Use=true VariantList=, STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Interesting, I have the exact same setup for years, and it's always been persistent for me. Unfortunately Kubuntu 23.04 ships Plasma 5.24 which is out of support at this time. Any chance you could upgrade to 5.27 somehow, and see if it's still happening there?
(In reply to Nate Graham from comment #1) > Interesting, I have the exact same setup for years, and it's always been > persistent for me. > > Unfortunately Kubuntu 23.04 ships Plasma 5.24 which is out of support at > this time. Any chance you could upgrade to 5.27 somehow, and see if it's > still happening there? I've upgraded to 23.10 which has Plasma 5.27.8. The Problem is still the same. For testing, could you replace your kxbrc file with the one I posted and re-boot? Then see if CapsLock is the compose key or not.
I'm pretty sure that "compose:caps" is contradictory with "caps:none" or "shift:both_capslock". Try unsetting one or both, rebooting, and seeing what happens.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!