Logitech MX Keys first keystroke is not taken

English Hardware
1

I have a Logitech MX Keys Combo with Logitech Bolt receiver. At every boot when I will enter my Password into SDDM the first keystroke is always lost. Either I have first to strock CTRL or ALT before I enter my password or login fails and I have to enter my password again. The second time it works. I’ve tried to disable USB-Autosuspend at startup (Kernel-Parameter) as well as this hint here from Google KI:

Fixes for SDDM Keyboard Focus Issues

But both with no success

2

Did you have that issue during install?
If, once SDDM is reached, unplug+replug the receiver, does the issue persist?

3

I can switch off the keyboard when SDDM is reached and switch it on again an then it works fine. It looks like that after a restart as well as at a new start the bolt receiver ignores the first keystroke respectively uses it to get back to work. If I unplug the bolt receiver before boot the bios cames up with a message that no keyboard is attached. So it looks that the bolt receiver tells the bios that there is a keyboard which is not enabled, it will be enable when the first keystroke is done, which is just used to connect the keyboard an will be discarded. From the second keystroke is done the connection between receiver and keyboard is established and the keyboard is fully funktional

4

Oops, I would not know how to debug that in some easy way.
Does the keyboard get activated when you hit Enter in Grub?

5

In GRUB, the keyboard is doing fine (switching with arrow keys between boot options). When after switching with arrow keys in GRUB SDDM appeared, the first keystroke for entering the password was always taken in this case. I assume that SDDM is the main problem which refuses to work with the hardware keyboard like it has a virtual keybord in the back that cannot be seen on the screen. Is there a option to get rid of SDDM if you want to use KDE-Plasma.

6

OK, new questions arise:

  • Is SDDM running via sddm.service or via default-displaymanager-legacy.service? Check both with systemctl status <service_here>`.
  • If the sddm unit is, then is it running on Wayland ?

If you haven’t changed anything, you probably still are running on default-displaymanager-legacy,meaning SDDM runs on X11, and it would be worthwhile to change that setup. Myself I am running SDDM on the sddm service unit and have a small snippet in /etc/sddm.conf.d which defines it to run on Wayland.

7

Thank you for your answer, sddm.service is not running here, it runs over this legacy service which can be changed over the alternative configuration in YaST. What do I have to put into /etc/sddm.conf.d to get everything to work fine. I found something in the Majaro Forum, but I’m not sure that this fits for opensuse, since I don’t want to risk a system that doesn’t starts again. Here the link to the Majaro forum:
Majaro SDDM

8

I switched with YaST → Alternatives to xdm and also to GDM and with both the first keystroke problem was gone. XDM is very basic but GDM looked like a suitable option for me. The problem here is, that it starts GNOME instead of Plasma. Sorry, but GNOME is not an option for me. Is there a way that GDM starts Plasma?

9

OK, here you go, before you start set the alternative in YaST back to SDDM. Then check whether the Plasma Wayland session is available in SDDM ( in the left botton corner from “Sessions”. It should be, login to that session. Make sure that plasma-wayland-protocols is installed. Next:

  • In SDDM hit Ctrl+Alt+F2, login as your user.
  • create a file called 10-wayland.conf with content:
[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1
  • Do: sudo systemctl disable --now display-manager-legacy.service
  • Do: sudo systemctl enable --now sddm.service
  • Do: sudo reboot

After the reboot you should see the difference as soon as SDDM shows up. I’m curious whether the keyboard issue still exists.

10

Thank you for you answer. Unfortunately it helps not. During boot the graphical SDDM login mask appears for a second and the it switches to text mode login. Entering the user name at the first try puts five times the same letter (from the first keystroke), login fails first, second try to login works, brings the text console and plasma has to be startet using the startx command.

11

Finally the solution for me was to switch over to autologin, since I’m the only person that can access this computer (except in case of a burglary which is not realistic since I live in the second floor), I can accept this situation.

12

Try startplasma-wayland instead. when starting from a terminal prompt. startx bringing up plasma on X11 but without the plasma environment variables. If you want Plasma on X11 start it with startplasma-x11.
To get a real proper solution, let’s wait what others come up with. Having a friend over later and I should start prepping for cooking.

13

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.