Bug 431430

Summary:	Mouse and keyboard not working until replugging on startup
Product:	[Plasma] kwin	Reporter:	Tobias Voigt <social>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kwin-bugs-null, nate
Priority:	NOR
Version First Reported In:	5.20.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Tobias Voigt 2021-01-11 10:49:10 UTC

SUMMARY
My mouse and keyboard are not working after logging in on LightDM until I re-plug them. This happens on every start and restart.

STEPS TO REPRODUCE
1. Restart/Start your system
2. Log in
3. You need to replug your mouse/keyboard to make them work again

OBSERVED RESULT
mouse and keyboard not working

EXPECTED RESULT
mouse and keyboard should work as expected without plugging them in again

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Manjaro
(available in About System)
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
My mouse is a Sharkoon Light 2 100 and my keyboard a Razer Blackwidow Chroma both plugged in directly to the motherboard. Every other usb device seems to be working.

Comment 1 Nate Graham 2021-01-11 22:47:28 UTC

So the mouse and keyboard work in LightDM, but stop working after you log in?

Is this on Wayland or X11? Or both?

Comment 2 Tobias Voigt 2021-01-12 07:18:00 UTC

Yes thats correct.
I just tested and in X11 everything works fine, but on Wayland not.

Comment 3 Bug Janitor Service 2021-01-27 04:33:24 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Vlad Zahorodnii 2023-01-17 13:07:16 UTC

Could you ssh to your computer, run

   sudo libinput debug-events

and try to use your mouse or keyboard and then post the output of libinput on this bug report?

Also, make sure that your input devices are not disabled in system settings? Also, can you check whether the issue is reproducible in 5.26?

Comment 5 Bug Janitor Service 2023-02-01 05:03:10 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2023-02-16 03:48:32 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!