Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#69121 - [libusb] Regression: some devices are no longer enumerated

Attached to Project: Arch Linux
Opened by Peter Wu (Lekensteyn) - Saturday, 26 December 2020, 18:50 GMT
Last edited by David Runge (dvzrv) - Sunday, 10 January 2021, 19:25 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To David Runge (dvzrv)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After upgrading from libusb 1.0.23-3 to 1.0.24-1, an iPhone failed to show up in lsusb and other places (usbmuxd).

I don't see anything worthwhile in the changelog (https://github.com/libusb/libusb/blob/v1.0.24/ChangeLog), so consider dropping/keeping this package in testing until upstream has solved this regression.

Additional info:
* package version: 1.0.24-1 (testing)
* Upstream bug report: https://github.com/libusb/libusb/issues/831

Steps to reproduce:
1. Run `lsusb -d05ac:` with an iPhone attached, expect an entry (see upstream for more details).
This task depends upon

Closed by  David Runge (dvzrv)
Sunday, 10 January 2021, 19:25 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with libusb 1.0.24-2 (currently in [testing]).
Comment by Peter Wu (Lekensteyn) - Sunday, 27 December 2020, 12:47 GMT
A was merged three days after the 1.0.24 release. Consider checking out from git (commit f6d2cb561402c3b6d3627c0eb89e009b503d9067) or apply this:
https://github.com/libusb/libusb/compare/v1.0.24...f6d2cb561402c3b6d3627c0eb89e009b503d9067.patch
Comment by David Runge (dvzrv) - Sunday, 10 January 2021, 19:08 GMT
@Lekensteyn: Thanks for the report. Sorry for the delay.. vacation and a load of package updates got in the way ;-)

It seems it should be no problem to apply the fix. I'll release a new pkgrel to [testing].

Loading...