I can’t use the USB file transfer functionality with iPhone in F41. I can see the `Documents` and `Photos` entries added in the Nautilus sidebar but clicking on `Documents` shows an error modal. I checked on an F40 machine this morning and the `Documents` folder works as normal. I've seen messages mentioning pairing failing and the iPhone keeps prompting me to "Trust" the computer every time I plug it in. This is what I see in journalctl (some bits redacted): Oct 26 11:36:10 davepc kernel: usb 1-2.2: new high-speed USB device number 11 using xhci_hcd Oct 26 11:36:10 davepc kernel: usb 1-2.2: New USB device found, idVendor=05ac, idProduct=12a8, bcdDevice=15.04 Oct 26 11:36:10 davepc kernel: usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 26 11:36:10 davepc kernel: usb 1-2.2: Product: iPhone Oct 26 11:36:10 davepc kernel: usb 1-2.2: Manufacturer: Apple Inc. Oct 26 11:36:10 davepc kernel: usb 1-2.2: SerialNumber: 0000XXXXXXXXXXXXXXXXXXXX Oct 26 11:36:10 davepc mtp-probe[152162]: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-2/1-2.2" Oct 26 11:36:10 davepc mtp-probe[152162]: bus: 1, device: 11 was not an MTP device Oct 26 11:36:10 davepc systemd[1]: /usr/lib/systemd/system/usbmuxd.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/usbmuxd.pid → /run/usbmuxd.pid; please update the unit file accordingly. Oct 26 11:36:10 davepc fwupd[4158]: 16:36:10.345 FuEngine failed to probe device usb:01:00:02:02: failed to get interfaces: USB error on device 05ac:12a8 : Entity not found [-5] Oct 26 11:36:10 davepc systemd[1]: Started usbmuxd.service - Socket daemon for the usbmux protocol used by Apple devices. Oct 26 11:36:10 davepc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=usbmuxd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Oct 26 11:36:10 davepc mtp-probe[152169]: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-2/1-2.2" Oct 26 11:36:10 davepc mtp-probe[152169]: bus: 1, device: 11 was not an MTP device Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.366][3] usbmuxd v1.1.1^20230720git61b99ab starting up Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.367][3] Successfully dropped privileges to 'usbmuxd' Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.367][3] Using libusb 1.0.27 Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.374][3] Initialization complete Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.374][3] Enabled exit on SIGUSR1 if no devices are attached. Start a new instance with "--exit" to trigger. Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.377][2] Skipping switch device 1-11 mode from 1 to 1 Oct 26 11:36:10 davepc usbmuxd[152168]: libusb: warning [op_get_configuration] device unconfigured Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.377][3] Found usbmux interface for device 1-11: 1 Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.377][3] Changing configuration of device 1-11: 0 -> 4 Oct 26 11:36:10 davepc kernel: ipheth 1-2.2:4.2: ipheth_enable_ncm: usb_control_msg: 0 Oct 26 11:36:10 davepc kernel: ipheth 1-2.2:4.2: Apple iPhone USB Ethernet device attached Oct 26 11:36:10 davepc NetworkManager[2123]: <info> [1729960570.4345] manager: (eth1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/13) Oct 26 11:36:10 davepc NetworkManager[2123]: <info> [1729960570.4373] device (eth1): interface index 13 renamed iface from 'eth1' to 'enpXXsXuXuXcXiX' Oct 26 11:36:10 davepc kernel: ipheth 1-2.2:4.2 enpXXsXuXuXcXiX: renamed from eth1 Oct 26 11:36:10 davepc NetworkManager[2123]: <info> [1729960570.4415] device (enpXXsXuXuXcXiX): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external') Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.442][3] Connecting to new device on location 0x1000b as ID 1 Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.442][3] Connected to v2.0 device 1 on location 0x1000b with serial number 0000XXXX-XXXXXXXXXXXXXXXX Oct 26 11:36:10 davepc NetworkManager[2123]: <info> [1729960570.4624] settings: (enpXXsXuXuXcXiX): created default wired connection 'Wired connection 1' Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.550][1] ERROR: Failed to read '/var/lib/lockdown/0000XXXX-XXXXXXXXXXXXXXXX.plist': No such file or directory Oct 26 11:36:10 davepc usbmuxd[152168]: [11:36:10.647][1] ERROR: Failed to read '/var/lib/lockdown/0000XXXX-XXXXXXXXXXXXXXXX.plist': No such file or directory Oct 26 11:36:11 davepc usbmuxd[152168]: [11:36:11.346][1] ERROR: Failed to read '/var/lib/lockdown/0000XXXX-XXXXXXXXXXXXXXXX.plist': No such file or directory Oct 26 11:36:11 davepc usbmuxd[152168]: [11:36:11.392][1] ERROR: Failed to read '/var/lib/lockdown/0000XXXX-XXXXXXXXXXXXXXXX.plist': No such file or directory Oct 26 11:36:11 davepc gnome-shell[3268]: Unable to mount volume Documents on David: Gio.IOErrorEnum: Unable to connect Oct 26 11:36:13 davepc usbmuxd[152168]: [11:36:13.818][1] np_callback: ERROR: Pair failed for device 0000XXXX-XXXXXXXXXXXXXXXX, lockdown error -5 Oct 26 11:36:14 davepc ModemManager[2110]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-2/1-2.2': not supported by any plugin Oct 26 11:36:15 davepc usbmuxd[152168]: [11:36:15.357][1] ERROR: Failed to read '/var/lib/lockdown/0000XXXX-XXXXXXXXXXXXXXXX.plist': No such file or directory Oct 26 11:36:20 davepc usbmuxd[152168]: [11:36:20.427][1] ERROR: Failed to read '/var/lib/lockdown/0000XXXX-XXXXXXXXXXXXXXXX.plist': No such file or directory Reproducible: Always Steps to Reproduce: 1. install Fedora 41 beta 2. connect iPhone to F41 machine via USB cable 3. on iPhone, say "Trust this Computer" when prompted 4. click `Documents` entry in Nautilus sidebar Actual Results: Error message in Nautilus window saying "Unable to connect" Expected Results: Nautilus is able to browse the iPhone `Documents` file system
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.