[Bug 1164616] New: Devices plugged into USB hub, that previously worked, stopped working the past few days
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616 Bug ID: 1164616 Summary: Devices plugged into USB hub, that previously worked, stopped working the past few days Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: Xmetal@protonmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Since around Feb 18-19, 2020, USB devices that previously worked, that were plugged into a usb hub, no longer seem to function. The TW install is updated pretty regularly (at least every few days), and if i run "dmesg" or "lsusb" the devices are recognized exactly by name and model number in the mouses case, but they do not function. I tried other distros on the same machine and this seems isolated to OpenSuse Tumbleweed (aka not say mouse or USB Hub failure) ... I also tried different 5.x serious kernels ... pretty much the latest kernels ... i do know i am on 5.5.4-1-default at the moment. each usb device works fine if i plug them DIRECTLY into either of my machines 2 usb ports directly, but as i said it SEEMS the install still detects when they are plugged in or not (and exactly what they are). While I posted on the forum, I am NOT the original poster but it seems someone else may be effected by this too https://forums.opensuse.org/showthread.php/539181-Inputs-not-used-through-US.... Since the day of install, everything was fine, so it did work for a long bit, versus this being a fresh install and it didn't work right away. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616#c3
Tobias Görgens
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616#c4
--- Comment #4 from Mike Smith
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616#c5
Hans Kuster
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616
Hans Kuster
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616#c8
--- Comment #8 from Mike Smith
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616#c9
--- Comment #9 from Tobias Görgens
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616#c10
--- Comment #10 from Tobias Görgens
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616
http://bugzilla.opensuse.org/show_bug.cgi?id=1164616#c11
--- Comment #11 from Mike Smith
Hey,
good news, I found a solution to make keyboard and mouse working again using a USB-Hub. It is, indeed, a systemd issue and I solved it by installing systemd 245 from this repo: https://build.opensuse.org/package/show/Base%3ASystem/systemd. Or the direct download link for systemd: https://software.opensuse.org/ymp/Base:System/openSUSE_Factory/systemd. ymp?base=openSUSE%3AFactory&query=systemd.
Afterwards, I could plug in my keyboard and mouse to the hub and they were fully functional! Could someone confirm that please? But it's still some kind of risk to install it on a daily driver since it's not an official release and may (probably) contain bugs! I just tested it on a USB-installation for a short period of time. So be aware. On the other hand, it's OpenSUSE and these packages shouldn't create too much trouble, I still can't guarantee it.
I hope it helps you!
I admit I was going to try that but installing that on a daily drivers (I admit I have not had any issues with Tumbleweed though as a rolling release) is not something I wanted to do. This is good to know and maybe this can show the OpenSuse dev team that a fix is on the way ... just have to wait for it to hit the normal TW repos for example -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com