Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1929148 - iPhone 7 not recognized and not charging with libusbx-1.0.24-1.fc33.x86_64
Summary: iPhone 7 not recognized and not charging with libusbx-1.0.24-1.fc33.x86_64
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libusbx
Version: 33
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Benjamin Berg
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-16 10:07 UTC by cooperbang
Modified: 2021-03-03 23:24 UTC (History)
7 users (show)

Fixed In Version: libusbx-1.0.24-2.fc33 libusbx-1.0.24-2.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-18 01:24:08 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github libusb libusb issues 831 0 None closed [Regression 1.0.24] Device is not enumerated on Linux 2021-02-16 10:36:01 UTC

Description cooperbang 2021-02-16 10:07:59 UTC 
Description of problem:
With libusbx-1.0.24-1.fc33.x86_64 iPhone 7 isn´t recognized by lsusb and usbmuxd anymore. 
It also doesn´t charge via USB-port anymore.

Version-Release number of selected component (if applicable):
libusbx-1.0.24-1.fc33.x86_64

How reproducible:
100%

Steps to Reproduce:
1. install libusbx-1.0.24-1.fc33.x86_64
2. plug iPhone 7 to USB port


Actual results:
phone doesn´t charge and isn´t recognized by lsusb and usbmuxd and libimobildevice utils

Expected results:
phone should charge and should be recognized by lsusb, usbmuxd and libimobildevice utils

Additional info:
With libusbx-1.0.23-2.fc33.x86_64 problem doesn´t occur
Comment 1 Benjamin Berg 2021-02-16 10:36:01 UTC 
This has been fixed in upstream commit https://github.com/libusb/libusb/commit/f6d2cb561402c3b6d3627c0eb89e009b503d9067
Comment 2 Fedora Update System 2021-02-16 22:54:20 UTC 
FEDORA-2021-046318b62d has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-046318b62d
Comment 3 Fedora Update System 2021-02-16 23:05:31 UTC 
FEDORA-2021-dbd6b8fb19 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-dbd6b8fb19
Comment 4 Fedora Update System 2021-02-17 05:59:49 UTC 
FEDORA-2021-dbd6b8fb19 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-dbd6b8fb19`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-dbd6b8fb19

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2021-02-17 06:03:08 UTC 
FEDORA-2021-046318b62d has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-046318b62d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-046318b62d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 LiZhenbo 2021-02-17 13:03:30 UTC 
I could no longer connect my iphone to F33 after updating to libusbx-1.0.24

FEDORA-2021-dbd6b8fb19 fixes this issue for me
Comment 7 Fedora Update System 2021-02-18 01:24:08 UTC 
FEDORA-2021-dbd6b8fb19 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 8 Fedora Update System 2021-03-03 23:24:35 UTC 
FEDORA-2021-046318b62d has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.