I currently have configured 2 keyboard layouts, moving a non-US keyboard at the top of the list. As I have yakuake starting automatically open on startup, I can start typing right away, and the layout is correct for a handful of seconds, and then changes to qwerty. Reproducible: Always Steps to Reproduce: 1. In system settings, Human Input Devices, add another keyboard layout: fr, French, French (Bepo, ergonomic, Dvorak way); 2. Move this variant up, so that it has precedence over the default US keyboard also present; 3. Restart (or logout, and login). Actual Results: Right after login, the keymap is correct, but only for 1 or 2 seconds, and then it's back to qwerty. In my case, launching "setxkbmap fr bepo" fixes it. Expected Results: The layout should be kept such as it is describes in the settings. If I remove the US keyboard, and the only layout is the new one I have set up, then all is well, and the right keyboard layout is selected.
Do you have ibus installed and running? it's known to reset the layout map There's a workaround in later version of Plasma 5 for this
I don't use ibus, but I use fcitx, which is an equivalent of what ibus does. Perhaps the workaround will also fix it for fcitx.
Created attachment 89945 [details] attachment-4204-0.html Unfortunately the workaround was only for ibus. The right fix would be for all IMs but that solution is not simple On Dec 12, 2014 6:38 PM, "Jiehong" <email@majiehong.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=341314 > > --- Comment #2 from Jiehong <email@majiehong.com> --- > I don't use ibus, but I use fcitx, which is an equivalent of what ibus > does. > > Perhaps the workaround will also fix it for fcitx. > > -- > You are receiving this mail because: > You are the assignee for the bug. >
What happens if you uninstall ibus? Does this solve your problem?
Hi there, obviously I cannot comment on behalf of the original author, but I think I faced the same issue on my setup. Removing Ibus solved the problem for me. Thanks for the hint! On a side note, here's one workaround I used often. I mention it because at least I was surprised when I discovered it: After login, when the plasma workspace was already visible but all sorts of applications were still starting, I quickly changed to an arbitrary virtual console (Ctrl+Alt+F4 and the like) and back to the graphical session - et voila, my desired keyboard layout was loaded. It even worked when the gnome keyring dialogue was shown, which in my case got the keyboard and mouse focus exclusively. I always thought that the fact that the workaround did work was a sign of a race condition at startup. Don't know if this description is of any value for others...
2022 one of the bugs on the graveyard of the bug.kde.org website still visible in plasma 5.23.5. Also the state is only reported!? This more annoying consider you use characters which position and composing is on various keyboard layouts different. This may cause several tries to enter it or even prevent you from logging in at plasma's login screen at all - depending on the fantasy of the user... I agree with the commenter's post from April last year, the description of this report may be for some not very obvious but its hard to describe in one line an issue which cant be simply described as "default language setting not respected" due to a missing "Default" indicator in systemsettings. So most users assume (without having read any documentation, only trust on their intuition) that, under the permissions that Global is selected, the top language in the list may (will) be the default one for all activities on the desktop.
Oh - I forgot the note that ibus is not installed on my system.
sorry, did not see this issue beforehand, but it might be related to what i just filed: https://bugs.kde.org/show_bug.cgi?id=470470