Bug 2321958
| Summary: | Fedora 41 beta breaks iPhone USB file transfer | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Bazile <david> |
| Component: | usbmuxd | Assignee: | Davide Cavalca <davide> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 41 | CC: | asahi-sig, benoit.ozell, cfergeau, da2ce7, davide, drusek, dustymabe, fnrd, iweiss, jhaiduce, johnandmegh, kohnish, mail, mig+redhat, philipcourier, rhbugzilla, rjwhite, svoboda77, toon.verstraelen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | usbmuxd-1.1.1^20240915git0b1b233-4.fc42 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-04-05 08:54:58 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
David Bazile
2024-10-26 20:48:51 UTC
I am seeing the same "Failed to read /var/lib/lockdown/..." issue on Fedora KDE 41 when trying to open my iPhone as a USB folder. Thanks for the report. /var/lib/lockdown isn't owned by any package, at the very least we need to fix ownership, and possibly check if selinux is doing something funny here. I will try to get a repro for this later in the week. (In reply to Davide Cavalca from comment #2) > Thanks for the report. /var/lib/lockdown isn't owned by any package, at the > very least we need to fix ownership, and possibly check if selinux is doing > something funny here. I will try to get a repro for this later in the week. Thanks! If it helps, I deleted the device-specific plist file from /var/lib/lockdown on my laptop still running F40, and confirmed that it still recreated it when the device was "trusted" on the iPhone (same phone same cable), while the Trust prompt never appeared on the device running F41. Seems weird since there were no code commits between F40 and F41, right? And I didn't see an immediate difference in SELinux logs - just a SERVICE_START and then SERVICE_STOP for both, no failures noted when grepping for usbmuxd. I think its related to libimobiledevice, they don't appear to have conventional versioning as its stuck at 1.3.0 in 2020 but the build used in Fedora appears to be an arbitrary later commit https://github.com/libimobiledevice/libimobiledevice I can dig out the other posts I made elsewhere if this would be useful? My first Red Hat Bugzilla interaction, so apologies. Links provided by the reporter of this bug (David Bazile), and another by Robert White, on the related Fedora Discussion posts led to seeing this from a couple of years ago: https://bugzilla.redhat.com/show_bug.cgi?id=2124349 where it was identified that without any modifications, libimobiledevice would be impacted by the change (in exploration at the time) to distrusting SHA-1 in signatures within Fedora. That change went into place in Fedora 41, which seems to be why this issue has appeared even though the package's source code itself didn't technically change between versions. I can verify on my system that if I run sudo update-crypto-policies --set FEDORA40 and reboot, then everything works as before - new devices can be trusted, and can be accessed through file managers (Dolphin for me on the KDE Spin). After reverting to DEFAULT, new devices can't be trusted, and the .plist files that were previously created are deleted from /var/lib/lockdown. The upstream issue opened as a result of that previous Fedora bug report is still open, with the last comment (https://github.com/libimobiledevice/libimobiledevice/issues/1355#issuecomment-1243296777) a couple years ago acknowledging that "this change actually might break pairing certificate generation in libimobile". The upstream issue that David opened (https://github.com/libimobiledevice/libimobiledevice/issues/1606) got comments mentioning that perhaps linking libimobiledevice with gnutls would be a way around this, but I'm novice enough on that topic to not be sure if that makes sense in this context/is feasible/etc. Davide, unless you discovered another side to the issue, perhaps it's a question of figuring out whether or not the alternate linking discussed in that latest upstream issue is an option? Thanks John! I was able to repro the issue and can confirm it can be worked around for now by running sudo update-crypto-policies --set FEDORA40 Which will downgrade the crypto policy to the f40 one. I'll review the issues upstream and look into a proper fix. Related threads on discourse for my reference: https://discussion.fedoraproject.org/t/fedora-41-beta-iphone-usb-file-transfer-stopped-working/ https://discussion.fedoraproject.org/t/fedora-41-beta-idevice-document-mounting-in-files-not-working/ > /var/lib/lockdown isn't owned by any package, at the very least we need to fix ownership Put up https://src.fedoraproject.org/rpms/usbmuxd/pull-request/2 to sort this out in the meantime. When an Iphone is Plugged in Via USB, File Explorer will not load. Is this still an issue? Yes, I installed Fedora 41 on a new laptop last week and had to use the same workaround on a fully updated system. I hit this problem today on an up-to-date F41 system. I will note the workaround in https://github.com/libimobiledevice/libimobiledevice/issues/1606#issuecomment-2543116644 at least is a good way to apply the workaround temporarily (if temporarily is good enough for you) without having to change your system settings. Is it possible to patch in this PR for libimobiledevice so that it can use SHA256? https://github.com/libimobiledevice/libimobiledevice/pull/1616 Very old iOS devices will continue to not work though since they can only use SHA1. Thanks JH, looking into this now. That PR won't work as-is, checking to see if it can be fixed. Put up https://src.fedoraproject.org/rpms/libimobiledevice/pull-request/4 but this needs testing (ideally together with https://src.fedoraproject.org/rpms/usbmuxd/pull-request/2). FEDORA-2025-0cf702b96b (libimobiledevice-1.3.0^20240916gited9703d-5.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-0cf702b96b *** Bug 2316127 has been marked as a duplicate of this bug. *** *** Bug 2351404 has been marked as a duplicate of this bug. *** FEDORA-2025-30a2239d21 (libimobiledevice-1.3.0^20240916gited9703d-5.fc42 and usbmuxd-1.1.1^20240915git0b1b233-4.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-30a2239d21 FEDORA-2025-0cf702b96b (libimobiledevice-1.3.0^20240916gited9703d-5.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-30a2239d21 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-30a2239d21` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-30a2239d21 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-30a2239d21 (libimobiledevice-1.3.0^20240916gited9703d-5.fc42 and usbmuxd-1.1.1^20240915git0b1b233-4.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. Yes, the problem persists, even after upgrading f41 to f42. (In reply to svoboda77 from comment #24) > Yes, the problem persists, even after upgrading f41 to f42. Interesting, I'm on Fedora 42 with update-crypto-policies --show returning "DEFAULT", and USB access to my iPhone is working fine. |