After update to 6.12.12 today I have major keyboard layout issues

Support System Updates
1

After today’s update to 6.12.12 (from 6.12.11), my previous keyboard settings which included EN and DE keyboard layouts were reset to EN only. I have to go the KDE keyboard menu to add DE manually. Then switching with the previous keyboard shortcut will work.
In addition to that, after a restart, those settings reset and I have to add DE again.

Also, I get a pop up stating that I should enable fcitx5 in the virtual keyboard menu. I did that and managed to add DE there as well. However, no keyboard shortcut works and if I switch from EN to DE in the task bar, the language typed does not change and stays at EN.

This is very unsatisfactory and seems like a bug or several. I’m on Wayland KDE with Plasma 6.2.5.

2 Likes
2

… not presuming anything:
did you check for .pacnew files and if there where some, did you merge them?

the result of:
localectl
could be helpful

and/or the result of:
grep -v ^# /etc/locale.conf

as well as:
grep -v ^# /etc/locale.gen

KDE/Plasma is always a little … different.
I don’t use it.

That is the approach I’d take with any other system/Desktop Environment.

3

localectl:

System Locale: LANG=en_US.UTF-8
               LC_NUMERIC=de_DE.UTF-8
               LC_TIME=de_DE.UTF-8
               LC_MONETARY=de_DE.UTF-8
               LC_PAPER=de_DE.UTF-8
               LC_NAME=de_DE.UTF-8
               LC_ADDRESS=de_DE.UTF-8
               LC_TELEPHONE=de_DE.UTF-8
               LC_MEASUREMENT=de_DE.UTF-8
               LC_IDENTIFICATION=de_DE.UTF-8
    VC Keymap: us
   X11 Layout: us

locale.conf yields the same information.

locale.gen:

de_DE.UTF-8 UTF-8
en_US.UTF-8 UTF-8

I don’t know what you mean by merging pacnew files or where to check for them. First time I’m hearing of them.

KDE/Plasma is always a little … different.

It’s popular, so it should have been tested I assume…

4

That’s not uncommon and o.k.
Go look.
It is important information when running Arch/Manjaro.

The us english keymap seems to be the default - but the german is also available.

I do not know why Plasma would do what you say it does with these. :man_shrugging:

5

I remember having the same issue on last update. I removed English in the KDE keyboard settings under assignments because it switched to EN automatically after reboot.

Once the language was removed, it worked as before.

6

I removed English in the KDE keyboard settings under assignments because it switched to EN automatically after reboot.

I checked that just now but it didn’t change anything.

did you check for .pacnew files and if there where some, did you merge them

There were some, inluding locale.gen.pacnew. I merged them all, but the issue remains. A restart resets my keyboard layouts to only EN.

1 Like
7

you have everything set to german - except for LANG

I find that strange and inconsistent - and would set it all to one and the same,
if not only for consistency’s sake
(everything else is set to german …)

… and have the second language available as well

/etc/locale.gen
defines what locales will be generated - and then later be available

sudo locale-gen
would then actually generate them

but that doesn’t seem to be the problem here

I don’t know what is.

8

Nothing I set. This is what you get with the Manjaro installer.

Something that happened with today’s update.

9

I slightly doubt: “This is what you get …” but … anyway …
(the initial ISO boot screen lets you choose language and country …)

Correct it regardless.
Or not.
Your choice.

you:

I still don’t know what the problem is. :man_shrugging:
I hope you’ll find out.

perhaps with:
GOTO beginning of post …

who knows?
I don’t.

Plasma UI has got it’s own settings possibilities.
I do not know hot they use these basic settings or how they interfere with them.

To me: it’s just a mess.
One reason for me not using it …

(not “the” reason - just one of them)

1 Like
10

Fcitx5 - Integration - Wayland - KDE Plasma | ArchWiki

Plasma on Wayland requires the input method process to be invoked by KWin. To achieve that, quit any running Fcitx 5 process, head to System Settings > Input Devices > Virtual Keyboard, then select Fcitx 5.

Fcitx5 - Configuration Tool | ArchWiki

The configuration file of fcitx5 is located at ~/.config/fcitx5. Although you can use a text editor to edit the configuration file, you might find a GUI configuration tool much more convenient, so install the fcitx5-configtool package.

11

I am using english and (two) serbian keyboard layouts. I had same problems as you so I removed fcitx5, fcitx5-qt5 and fcitx5-configtool to restore pre-update behaviour.

4 Likes
12

That “fixed” it, thank you!

So there’s quite an issue with fcitx5. fcitx5 itself does not work when it is installed and also hinders the legacy method to function properly.
I assume fcitx5 is supposed to be the correct way to go since 6.12.12. But in this state it is simply unusable.

13

That’s what I did. And the result is why I created this thread. So it doesn’t work.

14

Glad it helped.

1 Like
15

Hi,
I’m using gnome and I’ve the same troubles. How can I fix it?

Thanks

16

I guess in the same way?

17

Hi,
the thing is that if i do
localetcl it gives me this

System Locale: LANG=ca_AD.UTF-8
VC Keymap: es
X11 Layout: es
X11 Variant: cat

If I go to fcitx5 it gives me this layout:

[Groups/0]

Group Name

Name=“Per defecte”

Layout

Default Layout=us

Default Input Method

DefaultIM=keyboard-us

[Groups/0/Items/0]

Name

Name=keyboard-us

Layout

Layout=

[GroupOrder]
0=“Per defecte”

I tryed to change it but it doesn’t save the changes.
Somebody can help me?

Thanks

18

Please open a new issue

19

Finally I unistanstalled fcitx5 and it solved the issue.

Thanks!

1 Like
20

This is a bug in pamac that was triggered when running the last update via pamac with the AUR enabled, see https://forum.manjaro.org/t/input-method-current-users-input-method-forced-to-change/174431/37 (not limited to KDE/Plasma).

It resulted in the erroneous install of packages as build dependency of sdl2 even though sdl2 was actually removed. To confirm check pamac history if your update finished like this:
2025-02-17T10:16:34+0300] [ALPM] installed cmake (3.31.5-1)
[2025-02-17T10:16:33+0300] [ALPM] installed fcitx5 (5.1.12-1)
[2025-02-17T10:16:33+0300] [ALPM] installed jsoncpp (1.9.6-3)
[2025-02-17T10:16:33+0300] [ALPM] installed rhash (1.4.4-1)
[2025-02-17T10:16:33+0300] [ALPM] installed cppdap (1.58.0-2)
[2025-02-17T10:16:33+0300] [ALPM] installed wayland-protocols (1.39-1)
[2025-02-17T10:16:33+0300] [ALPM] installed xcb-imdkit (1.0.9-1)
[2025-02-17T10:16:33+0300] [ALPM] installed ninja (1.12.1-2)
[2025-02-17T10:16:33+0300] [ALPM] installed ibus (1.5.31-2)
[2025-02-17T10:16:32+0300] [ALPM] installed libibus (1.5.31-2)

The fix is, as mentioned above, to remove fcitx5, which is causing the input method issues. The other pkgs should show as orphans, just remove them as well.

1 Like