SUMMARY Regression compared to Plasma 5.27: Disabling the layouts deletes them STEPS TO REPRODUCE 1. Open System Settings. 2. Navigate to Keyboard. 3. Click on the Enable toggle to be able to add a few layouts. 4. Add one or more layouts. 5. Click on that Enable toggle again. OBSERVED RESULT The layout(s) are completely removed (deleted). So if you want to enable them again you will have to click again on the add button. Then search for the right language as they are so many. Then select the proper country / variant of the language. Then click OK to finally add it to the list. And that's just for one language. If you have 2-3 or more, then of course it's even more time wasted. EXPECTED RESULT Clicking on the toggle again makes it switch from the right side to the left side, which means the opposite of how it was before. The opposite of Enable is Disable, not remove or delete! Just because I want to disable something it doesn't mean I want to delete all the custom things I had to add. If I wanted to delete the layouts I would've deleted them one by one from their individual buttons where they properly have a "Remove" option. Before it was a checkbox instead of a toggle button and that didn't remove any layouts if it was unticked (unchecked). Which is what I consider normal and expected. BTW, why is a checkbox and now a toggle button required to have keyboard layouts? Isn't the fact that you add them enough to tell Plasma that you want / need them? Or it was supposed to be like adding them anytime and enable disable them depending on the situation? And why can't we just add them anytime without having to enable them? SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.7.2 Kernel Version: 6.12.13-amd64 (64-bit) Graphics Platform: Wayland HARDWARE SPECIFICATIONS Hardware: Laptop Dell Inspiron 5770 (17" 1080p@60Hz screen) CPU: Intel® Core™ i5-8250U CPU @ 1.60GHz GPU 1: Mesa Intel® UHD Graphics 620 (main) GPU 2: AMD Radeon R5 M465 Series RAM: 8 GiB (7.7 GiB usable)
I confirm the issue on 6.3.0.