kwin keymap issue after upgrading to plasma 5.21

lgtegetege · 2021-02-18 19:33:58

hello arch community, yesterday i updated plasma and after checking the journal, i found the following output:

Feb 18 12:57:12 lgtegetege kwin_x11[841]: kwin_xkbcommon: XKB: Couldn't process include statement for 'latam(\0)'
Feb 18 12:57:12 lgtegetege kwin_x11[841]: kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
Feb 18 12:57:12 lgtegetege kwin_x11[841]: kwin_xkbcommon: XKB: Failed to compile xkb_symbols
Feb 18 12:57:12 lgtegetege kwin_x11[841]: kwin_xkbcommon: XKB: Failed to compile keymap

im trying to figure out if there is this issue is causing any problem and what caused it, and like an hour ago i tried by restoring to a backup i made just before updating and i found that this issue started to happen just after i rebooted my system after updating. i dont know if anybody else is having this issue
Also this only happens in xorg, but i cant load the correct keymap in wayland

Last edited by lgtegetege (2021-02-18 20:15:38)

Sanras · 2021-02-19 01:03:22

Same issue here, I do not know what is causing this, but the latest Plasma update is likely at fault. I use the us layout

Feb 18 18:56:53 arkiron kwin_x11[863]: kwin_xkbcommon: XKB: Couldn't process include statement for 'us(\0)'
Feb 18 18:56:53 arkiron kwin_x11[863]: kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
Feb 18 18:56:53 arkiron kwin_x11[863]: kwin_xkbcommon: XKB: Failed to compile xkb_symbols
Feb 18 18:56:53 arkiron kwin_x11[863]: kwin_xkbcommon: XKB: Failed to compile keymap

Last edited by Sanras (2021-02-19 01:05:41)

johnjark · 2021-02-20 14:26:11

Confirm similar issue...
Feb 20 13:05:52 john-picasso kwin_x11[1090]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5110:46: this compose sequence is a duplicate of anothe>
Feb 20 13:05:52 john-picasso kwin_x11[1090]: kwin_xkbcommon: XKB: Couldn't process include statement for 'gb(\0)'
Feb 20 13:05:52 john-picasso kwin_x11[1090]: kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
Feb 20 13:05:52 john-picasso kwin_x11[1090]: kwin_xkbcommon: XKB: Failed to compile xkb_symbols
Feb 20 13:05:52 john-picasso kwin_x11[1090]: kwin_xkbcommon: XKB: Failed to compile keymap

seth · 2021-02-20 15:00:32

Can you please upload (do not copy and paste it!) ~/.config/kxkbrc ?
In doubt see the tip in the first link in my signature.

Sanras · 2021-02-20 16:48:59

seth wrote:

Can you please upload (do not copy and paste it!) ~/.config/kxkbrc ?
In doubt see the tip in the first link in my signature.

Here is my kxkbrc file - http://ix.io/2Q5O

Also another thing, I do not know if this is related, but likely to do with Plasma 5.21 as well. If I hit "restart", after I log back in and Plasma loads to the desktop, the screen will briefly flash black. Do you know how I could track down this issue?

Last edited by Sanras (2021-02-20 16:51:05)

Sanras · 2021-02-20 17:51:34

Alright, so I also have another PC (with very different hardware, it has a Xeon E5450, and RX 460 graphics, uses a USB keyboard) that also runs Arch Linux, which I haven't updated yet to Plasma 5.21.

So, I went ahead and did so, to see what would happen. Here is what I observed -

After updating to Plasma 5.21 and rebooting, the error did not appear in my logs (I remember this same thing happening on my laptop, which is where I first noticed this issue.), and everything seemed fine. So, I went ahead and restarted again. This time, the same error shows up in my logs -

Feb 20 11:39:24 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: Couldn't process include statement for 'us(\0)'
Feb 20 11:39:24 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
Feb 20 11:39:24 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: Failed to compile xkb_symbols
Feb 20 11:39:24 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: Failed to compile keymap

So, it seems that this issue appears across all installs of Plasma 5.21, or at least most of them.

I also noticed these errors (of a lower priority level, they will not show up with journalctl -p 3) that appear right before the errors listed above appear. They also did not appear before the 5.21 update, so it is likely related.

Feb 20 11:39:23 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5079:46: this compose sequence is a duplicate of another; skipping line
Feb 20 11:39:23 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5081:48: this compose sequence is a duplicate of another; skipping line
Feb 20 11:39:23 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5083:48: this compose sequence is a duplicate of another; skipping line
Feb 20 11:39:23 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5087:47: this compose sequence is a duplicate of another; skipping line
Feb 20 11:39:23 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line
Feb 20 11:39:23 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:48: this compose sequence is a duplicate of another; skipping line
Feb 20 11:39:23 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5101:46: this compose sequence is a duplicate of another; skipping line
Feb 20 11:39:23 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5103:46: this compose sequence is a duplicate of another; skipping line
Feb 20 11:39:23 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:45: this compose sequence is a duplicate of another; skipping line
Feb 20 11:39:23 arkalix kwin_x11[602]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5110:46: this compose sequence is a duplicate of another; skipping line

Last edited by Sanras (2021-02-20 17:54:38)

seth · 2021-02-20 21:08:42

VariantList=\\0

This looks bullshit and like the error you get (failed effort to print a 0 character?)

See what happens if you
- use "VariantList=intl"
- use "VariantList="
- just delete the key

GeorgeJP · 2021-02-20 21:38:44

I have similar issue.

~/.config/kxkbrc

looks good for me

http://ix.io/2Q7E

journalctl starts report problems after plasma and xkeyboard-config update on Feb 17

LC_ALL=C journalctl | grep XKB

http://ix.io/2Q7G

Sanras · 2021-02-21 16:55:09

seth wrote:

VariantList=\\0
This looks bullshit and like the error you get (failed effort to print a 0 character?)
See what happens if you
- use "VariantList=intl"
- use "VariantList="
- just delete the key

Changing "VariantList=\\0" to "VariantList=" does fix the issue. However, it only fixes the issue for one boot. I wrote changes to the kxkbrc file, and rebooted. At first, all looked well. There were no more errors in the logs, and the keyboard works fine. But when I took a look at the kxkbrc file again, I noticed that the line was changed back to VariantList=\\0 again for some reason. And sure enough, rebooting again causes the errors to show up in the logs again.

So, while deleting the \\0 from VariantList does work, it gets changed back by something after a reboot. Changing the key to "intl" means that it doesn't get overwritten to \\0, but intl causes another set of issues with my keyboard, even if no errors show up in the journalctl logs. Namely, the quote key doesn't work normally, I have to double tap it to make one quote symbol appear on screen. This doesn't happen when VariantList is set to \\0 or nothing.

Completely deleting the VariantList line also works fine. However, this causes the same behavior as setting it to nothing. "VariantList=\\0" just gets re-added to kxkbrc after a reboot.

Last edited by Sanras (2021-02-21 16:58:07)

seth · 2021-02-21 18:33:27

Try "VariantList=basic" (I just took a guess on the desired layout) and file a bug upstream.
As a temporary mitigation (if the above doesn't work) you could "sudo chattr +i ~/.config/kxkbrc" (makes it immutable and thus not writable, you'll have to "sudo chattr -i ~/.config/kxkbrc" later on to allow it being written by KDE)

Sanras · 2021-02-22 16:19:47

seth wrote:

Try "VariantList=basic" (I just took a guess on the desired layout) and file a bug upstream.
As a temporary mitigation (if the above doesn't work) you could "sudo chattr +i ~/.config/kxkbrc" (makes it immutable and thus not writable, you'll have to "sudo chattr -i ~/.config/kxkbrc" later on to allow it being written by KDE)

Thank you, "basic" was the correct setting for me. My keyboard now works fine, and there are no more errors in the logs. The VariantList= line hasn't been changed back to \\0 either. So, I did not have to make the file immutable.

flexusjan · 2021-03-21 23:38:38

Got the same Problem. Setting "VariantList=basic" solves it.

Should we open a bug-report for it? (I have never done this)

seth · 2021-03-22 06:27:19

https://bugs.kde.org/buglist.cgi?quicksearch=kxkbrc

Arch Linux

#1 2021-02-18 19:33:58

kwin keymap issue after upgrading to plasma 5.21

#2 2021-02-19 01:03:22

Re: kwin keymap issue after upgrading to plasma 5.21

#3 2021-02-20 14:26:11

Re: kwin keymap issue after upgrading to plasma 5.21

#4 2021-02-20 15:00:32

Re: kwin keymap issue after upgrading to plasma 5.21

#5 2021-02-20 16:48:59

Re: kwin keymap issue after upgrading to plasma 5.21

#6 2021-02-20 17:51:34

Re: kwin keymap issue after upgrading to plasma 5.21

#7 2021-02-20 21:08:42

Re: kwin keymap issue after upgrading to plasma 5.21

#8 2021-02-20 21:38:44

Re: kwin keymap issue after upgrading to plasma 5.21

#9 2021-02-21 16:55:09

Re: kwin keymap issue after upgrading to plasma 5.21

#10 2021-02-21 18:33:27

Re: kwin keymap issue after upgrading to plasma 5.21

#11 2021-02-22 16:19:47

Re: kwin keymap issue after upgrading to plasma 5.21

#12 2021-03-21 23:38:38

Re: kwin keymap issue after upgrading to plasma 5.21

#13 2021-03-22 06:27:19

Re: kwin keymap issue after upgrading to plasma 5.21

Board footer