https://bugzilla.suse.com/show_bug.cgi?id=1200983
Bug ID: 1200983 Summary: mouse & keyboard not available in X/plasma Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs@suse.de Reporter: opensuse@mike.franken.de QA Contact: gfx-bugs@suse.de Found By: --- Blocker: ---
Starting with a few Tumbleweed snapshots ago I always have the problem, that mouse and keyboard are not working in my X/plasma desktop. I always have to unplug und plug them in again. After that they work as expected. There are no obvious error messages, that could help me to solve this problem.
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c1
Stefan Dirsch sndirsch@suse.com 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 sndirsch@suse.com --- 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. :-(
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c2
--- Comment #2 from Stefan Dirsch sndirsch@suse.com --- And when does this happen? Right after reboot or also after a resume from STR/STD?
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c3
--- Comment #3 from Michael Hirmke opensuse@mike.franken.de --- (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.
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c4
Michael Hirmke opensuse@mike.franken.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(opensuse@mike.fra | |nken.de) |
--- Comment #4 from Michael Hirmke opensuse@mike.franken.de --- (In reply to Stefan Dirsch from comment #2)
And when does this happen? Right after reboot or also after a resume from STR/STD?
It happens whenever sddm starts, i.e. after every boot, init 3 / init 5, and also after resuming from hibernation. It does not happen after logging out and back in.
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c5
--- Comment #5 from Stefan Dirsch sndirsch@suse.com --- Thanks for reporting back! Unfortunately I have not explanation for this and no workaround either. :-( Let alone a fix ...
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c6
--- Comment #6 from Michael Hirmke opensuse@mike.franken.de --- Still exists, but only after a reboot, not after a resume from hibernation.
I get these messages in my log, but I don't think they are related:
systemd-udevd[1058]: hiddev0: /etc/udev/rules.d/50-hid.rules:5 Only network interfaces can be renamed, ignoring NAME="usb/%k"
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c7
--- Comment #7 from Michael Hirmke opensuse@mike.franken.de --- Created attachment 864591 --> https://bugzilla.suse.com/attachment.cgi?id=864591&action=edit journal entries regarding usb
https://bugzilla.suse.com/show_bug.cgi?id=1200983
Stefan Dirsch sndirsch@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|mouse & keyboard not |mouse & keyboard not |available in X/plasma |available in X/plasma after | |a reboot (needs replug the | |devices)
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c8
Stefan Dirsch sndirsch@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(opensuse@mike.fra | |nken.de)
--- Comment #8 from Stefan Dirsch sndirsch@suse.com --- 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.
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c9
--- Comment #9 from Michael Hirmke opensuse@mike.franken.de --- I suppose it is a kernel issue. It also happens in init level 3, but for the keyboard it is a bit different than for the mouse:
1. During boot the keyboard is usable as expected - one can chose the kernel to boot, enter the LUKS passphrase and so on. 2. As soon as the system is up, the keyboard lights go off. 3. The next keypress is ignored then. 4. After the second keypress the keyborad lights go on and one can use the keyboard again. 5. After a few seconds without keyboard usage the lights are switched off again and we restart at no 3.
Unplugging the keyboard and plugging it in again solves this problem. From then on the keyboard is working as expected.
As for the mouse: It doesn't work at all until it is unplugged an plugged in again.
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c10
Stefan Dirsch sndirsch@suse.com 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 sndirsch@suse.com --- 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.
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c11
--- Comment #11 from Michael Hirmke opensuse@mike.franken.de --- Still exists with kernel 6.1.12-1 and openSUSE Tumbleweed 20230225.
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c12
--- Comment #12 from Michael Hirmke opensuse@mike.franken.de --- (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.
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c13
Takashi Iwai tiwai@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com
--- Comment #13 from Takashi Iwai tiwai@suse.com --- (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?
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.
https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c14
--- Comment #14 from Michael Hirmke opensuse@mike.franken.de --- (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?
-
bugzilla_noreply＠suse.com