Keyboard problems after update

English Applications
1

Hi, this is my first post on the openSUSE Forums. Although I have worked with Linux a fair amount, I’d consider myself a bit of a newbie. Please forgive my ignorance.

I’ve been running openSUSE Tumbleweed for about two weeks now and although the learning curve has been a tad steep everything has been running smoothly and I’ve figured out all the issues that have come up until today. I ran ‘sudo zypper dup’ today and updated my install and a peculiar keyboard problem came up that I can’t figure out. When the Caps Lock key is on the Enter, Arrow keys, Ins-Home-Pgup-Del-End, and Backspace keys stop working. I’ve had to rollback the system with snapper.

I can’t get anything out of Google. Can someone point me in the right direction? Thanks.

2 Likes
2

Hi, welcome to these forums
To be honest, in all my years in support, I don’t think I’ve ever seen this. Which desktop environment are you running?

3

Bizarre isn’t? I’m running KDE.

4

Check the keyboard stuff in systemsettings. Also check keyboard settings in the BIOS.

5

Hi.
KDE running here and I have exactly the same behaviour since last zypper dup.
No idea how to fix it.

6

I’ve checked the system settings for the keyboard and tested a few different options, but no success. I’m running a Gigabyte motherboard. There are no keyboard related settings available to configure in the BIOS. Unfortunately Gigabyte locks away many settings in the BIOS.

7
  1. Have you tried a different keyboard?
  2. What kind of KB? (usb/bluetooth/etc?)
  3. Manufacturer? (MS, Logitech etc…)
  4. If you do a “real terminal” (ALT+F) does it make a difference?
  5. How about if you boot to runlevel 3 (console)
  6. USB, Bluetooth, dongle/either?
  7. If (Wayland) then X11 DE?

All else fails the start a kitty terminal and start another instance in that terminal with

kitty --debug-keyboard

this will start another instance and you can see the output in the first window

I also have a GigaByte MB circa 2012

8

Unfortunately I don’t have another keyboard to test. I’m using an Asus TUF K3 wired USB keyboard. The keyboard works fine pre-update, in the BIOS, and also works in Window$ (duel boot). Interestingly after changing runlevel the keyboard works perfectly, but on returning to GUI stops working properly. I ran kitty --debug-keyboard and the system is registering the keystrokes for the keys in question, however they don’t work.

9

Alright … sounds like a KDE thing … in systemsettings → keyboard I have multiple drivers that would probably work but I’m using the Logitech cordless desktop for my 112 key … I only see one ASUS driver … maybe try one of the generic ones?

10

I’ve tried the a few generic keyboard configurations, but not success.

11

Same problem. It seems to only happen on KDE related interface, e.g. login screen, dolphin.
Keyboard works on other apps fine.

12
4 Likes
13

Thanks so much! So it’s just a matter of waiting for a fix?

14

Libxkbcommon dev here. First of all, sorry for the inconvenience. An upgrade request has been send for Tumbleweed; it should land pretty soon. Meanwhile you may want to fallback to the previous snapshot or downgrade manually using packages from e.g. this page.

1 Like
15

Any estimate on when it’ll be fixed on OSS:TW? I’m not sure how to downgrade since your link provides the same version of libxkbcomon as in my installed version (1.9.0-1.1), or maybe I don’t know how to find older versions of a package using that link?

16

The version 1.8.0 disappeared indeed (some cache rule?).

The fix 1.9.2 landed in factory, so I believe it is going to be in the next snapshot.

If you cannot wait you may install the binaries manually, at your own risk.

17

Latest snapshot has version 1.9.2.

2 Likes