SUMMARY In wayland, after having set fcitx as virtual keyboard in "input device"/"virtual keyboard" in kde settings; the input method settings in "regional settings"/"input method" are not restored after restarting X, rebooting. STEPS TO REPRODUCE 1. go to "input device"/"virtual keyboard" in the kde settings manager and select "fcitx 5 Wayland Launcher" 2. go to "regional settings"/"input method" and select as per your convenience at least one layout that is not by default there and save the settings 3. restart X or the computer OBSERVED RESULT The settings in "regional settings"/"input method" are reset to default EXPECTED RESULT the user settings in "regional settings"/"input method" must be restored after X restart SOFTWARE/OS VERSIONS linux : slackware64 current with kernel 6.11.14 (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: 5.27.11 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.116 Qt Version: 5.15.15 ADDITIONAL INFORMATION
You say you're using Wayland but also talk about restarting X; can you clarify?
by mistake i said "restarting X" but i meant restarting the entire OS actually.
Thanks.
If you launch fcitx5 under wayland, it will take over the keyboard configuration. It needs to do that so that input methods and switching between them works. All changes that you make in System settings' Keyboard configuration may be overwritten. You can uninstall fcitx5 if you don't need its features (such as input in CJK languages) and use Plasma's configuration tools. If you do need fcitx5's features, you need setup the keyboard layouts and switching between them in fcitx5 (using kimpanel and/or kcm-fcitx5, for example). *** This bug has been marked as a duplicate of bug 357194 ***
Sorry for the noise, I was pattern-matching too quickly.
Sorry we were not able to get to this yet! Can you see if the issue still happens in Plasma 6.3.5 or later? Thanks a lot!
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME.