There is an issue that libheif cannot convert photos taken by iphone15 as reported in https://github.com/strukturag/libheif/issues/1190 and fixed in the latest version. Please update libheif The packages are: libheif-1.17.6-1.fc40.x86_64 libheif-tools-1.17.6-1.fc40.x86_64 Reproducible: Always
I think the issue has a larger scope than defined. It is my understanding that all pictures taken with Apple devices running iOS 18 (the current version) and exported as originals (*.HEIC) cannot be viewed, edited, or converted on Fedora <= 41. So a lot of users may be delighted by such an update. Thanks a lot for looking into it.
Yeah, this has been reported on mastodon too: https://fosstodon.org/@razze@osna.social/113962353983994440 Upstream changelog for 1.18.0 says "now reads images generated by iOS 18". 1.19.0 says "The major new feature in this release is the decoding of separate image tiles and also encoding an image tile by tile" and that it supports three tiling methods; not sure the real world impact of that, but it seems useful. 1.18.x and 1.19.x updates were maintenance/bugfix. It doesn't look like there are any ABI changes, at least the soname wasn't bumped. (I was a bit concerned about "decoding progress is signaled to the client application and decoding can be cancelled", but looking at the code for that change, it appears to only change private functions, and the 'signalling' is done via stdout). So it should be safe to update this. Technically it might be good to request an update policy exception for this - the update policy says, for stable releases, "Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience" - though in this case I'd say it's a bit debatable; from one perspective the update would be "introduc[ing] features", but from another it'd be "fix[ing] bugs". I'll poke Neal and Dominik (who seems to have been most active in updating the package lately) about this elsewhere if I can.
I think we can go ahead and just do the update. We went through compatibility checks when updating in rawhide some time ago. FWIW, here are some sample images that don't work with 1.17.6, but start working after updating to 1.19.x: https://github.com/mastodon/mastodon/issues/31570 -> https://github.com/user-attachments/files/16734152/HEIF-images.zip . I'll mention those in the update notes for testers.
FEDORA-2025-666aaa6a0d (libheif-1.19.5-3.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-666aaa6a0d
FEDORA-2025-8fdb7be3cb (libheif-1.19.5-3.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-8fdb7be3cb
FEDORA-2025-8fdb7be3cb has been pushed to the Fedora 41 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-8fdb7be3cb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8fdb7be3cb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-666aaa6a0d has been pushed to the Fedora 40 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-666aaa6a0d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-666aaa6a0d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
@dominik Please fast-forward the F42 branch as well?
(In reply to Miloš Komarčević from comment #8) > Please fast-forward the F42 branch as well? Done.
FEDORA-2025-666aaa6a0d (libheif-1.19.5-3.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-8fdb7be3cb (libheif-1.19.5-3.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.