https://bugs.kde.org/show_bug.cgi?id=450117
--- Comment #19 from Michael <michael.nos...@gmx.de> --- I've looked again into my problem. I tried to fix all warnings reported by exiftool - without success. Kodi under linux reports these additional two errors IptcParse: Unrecognised IPTC tag: 0x41 IptcParse: Unrecognised IPTC tag: 0x46 Deleting all IPTC tags using exiftool fixed those error messages, but the jpg is still not visible within kodi under osmc on a raspberry. Thus I assumed that maybe the picture dimension triggers a memory problem within raspberry. But I can prove the contrary. I've converted the buggy jpg into tiff and back again into jpeg using imagemagick's convert. Now all EXIF metadata are really gone, and the jpg is visible within kodi on my raspberry. If I finally copy all exif information back using exiftool that jpg works fine within kodi on raspberry including exif metadata. I don't understand why my buggy jpg fails on kodi@raspberry (osmc based upon kodi 19.4) while working fine on kodi@linux (also kodi 19.4) and digikam 7.6.0. But I'm quite sure that my problem is triggered by digikam 7.6.0 if it does an automatic rotation. These seem to be the differences between the fixed and the buggy jpgs as reported by exiftool 12.39: fixed jpg: Validate : 1 Warning (minor) Warning : [minor] Non-standard IFD0 tag 0x000b ProcessingSoftware buggy jpg (the one uploaded): Validate : 4 Warnings (all minor) Warning : [minor] Non-standard IFD0 tag 0x000b ProcessingSoftware Warning : [minor] Fixed incorrect URI for xmlns:MicrosoftPhoto Warning : [minor] IFD0 tag 0x0100 ImageWidth is not allowed in JPEG Warning : [minor] IFD0 tag 0x0101 ImageHeight is not allowed in JPEG Additionall the preview images and the makernotes are dropped within the fixed jpg. Hope that you might discover the change within digikam. Regards, Michael -- You are receiving this mail because: You are watching all bug changes.
