Fedora 41 Beta - iDevice Document mounting in Files not working

With the upgrade to Fedora 41 Beta the “Documents” mounting on iOS devices is giving an “Unable to connect” error.

This is after the previous trusted iDevice requests to trust Fedora again.

I’m unsure how to diagnose. I think its gvfs and I think can use gio to attempt to recreate on cli… not sure where to start.

Happy to report with the project directly, if I knew which one.

I know its not directly ifuse as that is not installed and I believe gvfs has that within it somehow…

Raised a case on GNOME Files GitLab here: iDevice "Documents" mounting not working (#3588) · Issues · GNOME / Files · GitLab

Hopefully, given it’s possibly gvfs related this is the right place…

After some debugging on gvfs it appears to be an issue with libimobiledevice, where I raised this case ERROR: Could not connect to lockdownd: SSL error (-5) · Issue #1606 · libimobiledevice/libimobiledevice · GitHub

The suggest appears to build a newer version than the one supplied with Fedora 41 Beta, I can see the “Release” is from 2020 but there are plenty of tweaks since then.

How did I find someone in Fedora to investigate?

I can see the current Fedora 41 Beta build (1.3.0^20230705git6fc41f5) is from a commit - tools/idevicecrashreport: Silence compiler warning · libimobiledevice/libimobiledevice@6fc41f5 · GitHub so not the “Release”.

I have the same issue but didn’t see your topic until just now:

Thread:

Bug Ticket:
https://bugzilla.redhat.com/show_bug.cgi?id=2321958

2 Likes

This is great, because I had no idea where to actually genuinely get it in front of the right people.

FWIW, this bug also seems to cause crashes in the Save As… dialog, at least in some KDE apps - I noticed that Spectacle, the KDE screenshot tool, was crashing when I chose Save As, then noticed that the top of the stack in the crashed process was libimobiledevice…and sure enough, unplugging my iPhone fixed the problem.

In case that is helpful to anyone!

As mentioned in the ticket and in the other thread, for the time being the issue can be worked around by running sudo update-crypto-policies --set FEDORA40, which will downgrade the crypto policy to the f40 one.

1 Like

While sudo update-crypto-policies --set FEDORA40 also solves the problem for me, can anyone explain what’s the security implication of such downgrade? What components does it affect other than libimobile?