https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #26 from Loic <loickern...@gmail.com> --- I further digged into this issue and used your infrastructure into project/bundles/appimage to build an appimage with an updated version of ffmpeg. Currently the platform you use to build appimages (Mageia 7) ships a 4.1.x version of ffmpeg, while Mageia ships a 4.3.x version. I backported and built the 4.3.x version into Mageia 7 and built an appimage using your scripts, changing nothing else than ffmpeg. I would gladly share this appimage with you and can send a temporary wetransfer link on your private mail. Results are, as I anticipated, that there is no crash with the official-ffmpeg4.1 appimage, while the crahs described in this bug report can be observed with a custom-ffmpeg4.3 appimage. What is strange and interesting though is the following : crashes are observed when starting a new digikam-ffmpeg4.3 setup (i.e. erasing all .db files and digikamrc file before starting, with the two test files in the images directory and (double)clicking first on th jpeg, then on the vertical .mov). Now, if I start a new digikam-ffmpeg4.1 setup, there is no crash, as I said, but if after that I start digikam-ffmpeg4.3 without erasing .db files and digikamrc, there is no crash either. So, I have a question : is ffmpeg used in any form when building the databases (like size, orientation, etc) to set data which would then used by qtav for playback ? Is there a way I could access and analyse the database content differences in the two setups above ? -- You are receiving this mail because: You are watching all bug changes.
