Bug 2056326
| Summary: | 1.0.25-4.fc37 breaks yubikey and fingerprint reader | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kevin Fenzi <kevin> |
| Component: | libusb1 | Assignee: | Benjamin Berg <bberg> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | bberg, gryt2, hdegoede, jnovy, jv+fedora, lucilanga, rhbugs, victortoso |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-02-22 13:17:50 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: | |||
|
Description
Kevin Fenzi
2022-02-21 02:00:02 UTC
*** Bug 2056322 has been marked as a duplicate of this bug. *** I'm seeing this too with a nitrokey start, systemctl status pcscd says: Feb 21 12:02:21 x1.localdomain pcscd[16446]: 00000000 ccid_usb.c:863:WriteUSB() write failed (1/14): -4 LIBUSB_ERROR_NO_DEVICE Downgrading to 1.0.25-3 fixes things. Yes, libusb1 is currently horribly broken and I am really sorry for not pushing out fixes earlier. I spent time on finding a long-term solution instead of reverting the problematic parts of the upstream changes (this includes working on new CI tests for libusb upstream). There are two upstream changes causing major issues: 1. Logging now dereferences to the context more often, causing multiple use-after-free situations (two different cases) 2. libusb_init(&ptr) doesn't set a global context anymore, causing crashes on API misuse (bug #2055504) Then, one of the patches I did for 1. caused the synchronous API to completely break, which is likely the reason that most people are coming this way. I'll prepare an update now with three new patches. 1 & 2 are the fixed versions for issue #1. Then, a third new patch to revert the behaviour change of libusb_init(&ptr), to implicitly use the first created context as the default one when available. I'll remove the third patch again as soon as gutenprint bug #2055504 is addressed. OK, this should be fixed by: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b445cd59eb and https://bodhi.fedoraproject.org/updates/FEDORA-2022-b8a20d6a06 I'll back out the ugly workaround for the gutenprint bug as soon as that is resolved. Other than that, we have much more comprehensive testing using umockdev (as submitted upstream) which are run both during RPM build and as a gating test. I hope that future updates will not result in as much breakage and I hope there will be no further fallout from this update. Thank you I can confirm that things work again for me with libusb1-1.0.25-8.fc36 . Same here, thanks for the quick fixes! |