https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c1 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS CC| |opensuse@mike.franken.de Flags| |needinfo?(opensuse@mike.fra | |nken.de) --- Comment #1 from Stefan Dirsch --- Hmm. Could you provide your Xserver logfile? Could be somewhere below ~/.local/share/sddm or alike. I'm afraid sddm no longer uses /var/log/Xorg.0.log. :-( -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c3 --- Comment #3 from Michael Hirmke --- (In reply to Stefan Dirsch from comment #1)

Hmm. Could you provide your Xserver logfile? Could be somewhere below ~/.local/share/sddm or alike. I'm afraid sddm no longer uses /var/log/Xorg.0.log. :-(

It is not sddm only. Sometimes the keyboard is working, so I can login. But in plasma still the mouse does not work. There are these error messages in Xorg.0.log: [ 125.027] (EE) Wacom HID 48EC Pen stylus: Invalid type 'cursor' for this device. [ 125.027] (EE) Wacom HID 48EC Pen stylus: Invalid type 'touch' for this device. [ 125.027] (EE) Wacom HID 48EC Pen stylus: Invalid type 'pad' for this device. ... [ 5474.526] (EE) event4 - Fujitsu Siemens Computers SmartCard Keyboard USB 2A: client bug: event processing lagging behind by 22ms, your system is too slow ... [ 7189.743] (EE) event4 - Fujitsu Siemens Computers SmartCard Keyboard USB 2A: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c5 --- Comment #5 from Stefan Dirsch --- Thanks for reporting back! Unfortunately I have not explanation for this and no workaround either. :-( Let alone a fix ... -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c7 --- Comment #7 from Michael Hirmke --- Created attachment 864591 --> https://bugzilla.suse.com/attachment.cgi?id=864591&action=edit journal entries regarding usb -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c8 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(opensuse@mike.fra | |nken.de) --- Comment #8 from Stefan Dirsch --- Since this now already happens after reboot. Can you check with the keyboard whether this also happens in the Linux console, i.e. into runlevel 3 before the desktop starts? https://tutorialforlinux.com/2020/10/07/how-to-boot-opensuse-15-on-runlevel-... I would like to know if this is already a kernel issue or related to X11. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c10 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X.Org |Kernel Assignee|gfx-bugs@suse.de |kernel-bugs@opensuse.org Summary|mouse & keyboard not |mouse & keyboard not |available in X/plasma after |available after a reboot |a reboot (needs replug the |(needs replug the devices) |devices) | QA Contact|gfx-bugs@suse.de |qa-bugs@suse.de Flags|needinfo?(opensuse@mike.fra | |nken.de) | --- Comment #10 from Stefan Dirsch --- Thanks for testing. Indeed this makes it a kernel issue. You could also test the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is a bit complicated to figure out the right device. So I only wanted to mention keyboard here. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c12 --- Comment #12 from Michael Hirmke --- (In reply to Stefan Dirsch from comment #10)

Thanks for testing. Indeed this makes it a kernel issue. You could also test the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is a bit complicated to figure out the right device. So I only wanted to mention keyboard here.

Keyboard and mouse both have problems one the console, too. The keyboard vanishes after a few seconds and returns, as soon as a key is pressed, but the first keypress is not shown. The mouse never works on the console - no events are shown. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c14 --- Comment #14 from Michael Hirmke --- (In reply to Takashi Iwai from comment #13)

(In reply to Michael Hirmke from comment #12)

...

(In reply to Stefan Dirsch from comment #10)

...

Thanks for testing. Indeed this makes it a kernel issue. You could also test the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is a bit complicated to figure out the right device. So I only wanted to mention keyboard here.

Keyboard and mouse both have problems one the console, too. The keyboard vanishes after a few seconds and returns, as soon as a key is pressed, but the first keypress is not shown. The mouse never works on the console - no events are shown.

What do you mean "vanishes" here? It means that the /dev/input/event* device is gone?

no, there is no mouse pointer and the keyboard light is off.

The point to check here is whether the device file persists and can read/write from a user-space (no matter whether it's processed or not). Or is the (USB?) audio device itself disappears and reappears automatically.

Because the keyboard also has problems, this isn't easy to debug. What exactly would you like me to test? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c16 --- Comment #16 from Takashi Iwai --- (In reply to Michael Hirmke from comment #14)

(In reply to Takashi Iwai from comment #13)

...

(In reply to Michael Hirmke from comment #12)

...

(In reply to Stefan Dirsch from comment #10)

...

Thanks for testing. Indeed this makes it a kernel issue. You could also test the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is a bit complicated to figure out the right device. So I only wanted to mention keyboard here.

Keyboard and mouse both have problems one the console, too. The keyboard vanishes after a few seconds and returns, as soon as a key is pressed, but the first keypress is not shown. The mouse never works on the console - no events are shown.

What do you mean "vanishes" here? It means that the /dev/input/event* device is gone?

no, there is no mouse pointer and the keyboard light is off.

...

The point to check here is whether the device file persists and can read/write from a user-space (no matter whether it's processed or not). Or is the (USB?) audio device itself disappears and reappears automatically.

Because the keyboard also has problems, this isn't easy to debug. What exactly would you like me to test?

If you have two USB keyboards, you can check it if a problem happens only a single one or on both. Also, if you can access remotely e.g. via ssh, it can be checked without interrupting the input device status, too. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c18 --- Comment #18 from Takashi Iwai --- (In reply to Michael Hirmke from comment #17)

All USB keyboards and mice are affected.

Do I understand correctly that, when you login via sddm, all USB keyboards and mouses don't work, no matter how many keyboards / mouses are connected? And, if you reconnect one of them, do they all start working? Or it's only the reconnected one?

And yes, Iit is possible to access the machine via ssh. What exactly do you want me to check then?

At the moment you have no input control after SDDM login, login via ssh. Then get the dmesg output at first. You can get the hwinfo output at this moment, too. Run evtest as root and check whether the corresponding input device appears there, and test whether the input reacts. If the input still doesn't work on the screen, reconnect. And confirm that it's working, then get the dmesg output and hwinfo output. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c20 --- Comment #20 from Takashi Iwai --- (In reply to Michael Hirmke from comment #19)

(In reply to Takashi Iwai from comment #18)

...

(In reply to Michael Hirmke from comment #17)

...

All USB keyboards and mice are affected.

Do I understand correctly that, when you login via sddm, all USB keyboards and mouses don't work, no matter how many keyboards / mouses are connected? And, if you reconnect one of them, do they all start working? Or it's only the reconnected one?

No, there is alway only one mouse and one keyboard connected, but I tried 3 different keyboards and 2 different mice - and all of them show the same behaviour.

So, if you connect two USB keyboards, both are gone? Also, it happens no matter which port is used? I guess both yes, but such a thing is worth to test. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c22 --- Comment #22 from Michael Hirmke --- Created attachment 866042 --> https://bugzilla.suse.com/attachment.cgi?id=866042&action=edit latest journal entries regarding usb The log contains all "usb" entries from the last boot. All devices are found during boot. The keyboard works in grub and in the plymouth dialog for the LUKS passphrase. All /dev/event entries are present. There are no errors or warnings in the log regarding usb. At Apr 01 12:13:32 the boot process finished and the sddm login screen was shown. At this point according to the journal still all devices were present (also checked the presence of the devices from remote), but keyboard and mouse didn't work as expected. Using a linux console the keyboard misbehaved as described in https://bugzilla.suse.com/show_bug.cgi?id=1200983#c10. Returning to sddm login, keyboard and mouse didn't work at all. At Apr 01 12:34:19 I disconnected and reconnected keyboard and mouse and both started working immediately. If you need more logging or more debugging, ... -- You are receiving this mail because: You are on the CC list for the bug.