Bug 1800820

Summary: Keyboard/Mouse behind USB hub not working in GDM/Gnome after systemd upgrade
Product: [Fedora] Fedora Reporter: Gianluca Merlo <gianluca.merlo>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: gwirth79, leon, lnykryn, msekleta, ssahani, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-245~rc1-2.fc32 systemd-243.7-1.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-15 02:17:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Xorg.0.log with USB2.0 hub mouse failure
none
dmesg output with systemd-243.6-1.fc31.x86_64 and USB2.0 hub mouse failure
none
output of lsusb -vv showing USB2.0 hub and mouse none

Description Gianluca Merlo 2020-02-08 00:38:12 UTC
Description of problem:

After upgrading systemd to systemd-243.6-1.fc31.x86_64, a keyboard and mouse connected to a USB hub are powered but no longer working in GDM and Gnome. They work if connected directly to USB ports of the system.
If I connect them directly, switch to a VT, and re-connect them to the hub they are correctly working.
udev seems to see them fine when connecting/disconnecting from the hub, libinput and Xorg do not.
Suspecting systemd (systemd-udev, or systemd-logind, though I am very , I downgraded to systemd-243-4.gitef67743.fc31.x86_64, which fixes the issue.

Version-Release number of selected component (if applicable):

systemd-243.6-1.fc31.x86_64

How reproducible:

Steps to Reproduce:
1. Connect devices to usb hub
2. Boot the system

Actual results:

At GDM login screen, mouse and keyboard are not working.

Expected results:

Mouse and keyboard should be working.

Additional info:

USB Hub is a rather plain AmazonBasics 10-port USB 2.0 hub
A USB headset device connected to the same hub works fine, issue seems to be with HID only.

Comment 1 Gus Wirth 2020-02-10 05:20:39 UTC
Created attachment 1662035 [details]
Xorg.0.log with USB2.0 hub mouse failure

This Xorg.0.log file is with systemd-243.6-1.fc31.x86_64

Comment 2 Gus Wirth 2020-02-10 05:22:52 UTC
Created attachment 1662036 [details]
dmesg output with systemd-243.6-1.fc31.x86_64 and USB2.0 hub mouse failure

Comment 3 Gus Wirth 2020-02-10 05:25:35 UTC
Created attachment 1662037 [details]
output of lsusb -vv showing USB2.0 hub and mouse

Comment 4 Gus Wirth 2020-02-10 05:35:59 UTC
I have the same issue. After upgrading from systemd-243.5-1.fc31.x86_64 to systemd-243.6-1.fc31.x86_64 the mouse stopped working when plugged into a USB2.0 hub. Plugging the mouse into a USB port directly connected to the motherboard worked.

If I switch to a virtual console and use gpm (general purpose mouse), the mouse works fine.

Downgrading the systemd-* packages to the systemd-*243.5-1.fc31.x86_64 versions fixes the problem.

Comment 5 Zbigniew Jędrzejewski-Szmek 2020-02-10 16:27:49 UTC
https://github.com/systemd/systemd/issues/14822

Comment 6 Fedora Update System 2020-02-11 20:39:01 UTC
FEDORA-2020-87abf68a78 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-87abf68a78

Comment 7 Fedora Update System 2020-02-12 01:57:39 UTC
systemd-243.7-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-87abf68a78

Comment 8 Fedora Update System 2020-02-15 02:17:23 UTC
systemd-243.7-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.