Created attachment 176500 [details] picture which triggers the issue SUMMARY When previewing *some* jxl files, the preview window just shows a 'Failed to load image' information. The same image can be viewed with the 8.4.0 snap version and also with 8.5.0 AppImage. STEPS TO REPRODUCE 1. Download attached picture and save to one of your albums 2. Open the album and switch to the preview window 3. Click on the picture to activate the preview for the given picture 4. Observe failure message on top right corner of the preview area OBSERVED RESULT Image preview stays blank EXPECTED RESULT Preview of the selected Image SOFTWARE/OS VERSIONS Operating System: Kubuntu 24.10 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.6.2 Kernel Version: 6.11.0-9-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6600 CPU @ 3.30GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 ADDITIONAL INFORMATION I can provide an additional image which is in jxl format which does not trigger this behavior. This behavior was also observed by my brother on another computer (also running Ubuntu). He also confirmed that this issue is present in x11 as well as in wayland.
Created attachment 176501 [details] jxl image which does not trigger the issue adding a picture which does not trigger the issue. This picture will be rendered just as expected.
digiKam loads JXL images with the KImageFormat plugins. Please report the problem together with the sample image there. Unexpected event 16384 instead of JXL_DEC_COLOR_ENCODING Maik
I can reproduce the problem here under openSUSE. The image can be loaded in our AppImage. I suspect that it has something to do with the compile-time configuration of libjxl. Since Gwenview or Okular are also affected, I'm moving it to the KImageFormat plugins. Maik
Fixed in KF 6.9 (once it releases)
Thanks to both of you. I just realized, that I also can´t export these jxl files. This also works, on the 8.4.0 snap. Do you know if this is for the same reason and therefore also already fixed? Or if I should make a new bug report (haven´t searched jet if I find some thing similar in the tracker though).