https://bugs.kde.org/show_bug.cgi?id=389690
--- Comment #4 from e...@coloursofdiscovery.com --- First thanks for all the responses and sorry for my late reply. Is this problem to reproduce with all JPEG files or only with certain ones? I did not experiment yet, the system was meant to be a production environment. Can you provide a test image and the output of the console? Sure your hard drive has no problems? Here is a link to download the affected jpg's and the unaffected ones each side: https://cloud.zenquest.co/index.php/s/KfaQCGDPfts5Ybb I can try running digikam 5.9.0 on a range of images and report back with the backtrace. However I don't even know what GDB stands for! What is the syntax for starting a digikam.diskimage from the console with GDB backtrace? Many thanks -- You are receiving this mail because: You are watching all bug changes.
