Created attachment 147569 [details] win10 eventlog SOFTWARE/OS VERSIONS Windows: Windows 10 Home Version 21H2 build 19044.1586
The attached file is not suitable/viewvable. Please run debugview tool from Microsoft and catch the debug traces from digiKam while reproduce this dysfunction. More info here : https://www.digikam.org/contribute/
Created attachment 147577 [details] HP-LUTZ.LOG I used Dbgview64a.exe to create the attached file HP-LUTZ.LOG Am 17.03.2022 um 22:16 schrieb bugzilla_noreply@kde.org: > https://bugs.kde.org/show_bug.cgi?id=451637 > > --- Comment #1 from caulier.gilles@gmail.com --- > The attached file is not suitable/viewvable. > > Please run debugview tool from Microsoft and catch the debug traces from > digiKam while reproduce this dysfunction. > More info here : > > https://www.digikam.org/contribute/ >
There are plenty of system exceptions in the background which are nothing to do with digiKam, but there can introduce side-effects. Something is wrong on your system. Gilles Caulier
Just a small excerpt, You have defective JPG files, although digiKam shouldn't crash, but that will probably be the reason. digikam.dimg.jpeg: Invalid JPEG file structure: two SOI markers digikam.dimg.jpeg: Unsupported marker type 0x50 digikam.dimg.jpeg: Unsupported marker type 0x04 Maik
Created attachment 147582 [details] HP-LUTZ-1.LOG Hello Mike, thank you very much for the answer. I saw in the log sent yesterday that my folder structure also contained two wav files. I have deleted them. You have noted that there is at least one defective jpg file. However, the message "Invalid JPEG file structure: two SOI markers" does not indicate which file(s) it could be. My question: is there a way for me to create my own log file in digiKam that I can use to find the file with the "Unsupported marker type 0x50" and "Unsupported marker type 0x04"? Today the programme simply quit again. Enclosed is the LOG file. Yours sincerely, Lutz Doering. One more question: Your name indicates knowledge of the German language. May I write to you in German? Translated with www.DeepL.com/Translator (free version) Am 18.03.2022 um 10:19 schrieb Maik Qualmann: > https://bugs.kde.org/show_bug.cgi?id=451637 > > Maik Qualmann <metzpinguin@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |metzpinguin@gmail.com > > --- Comment #4 from Maik Qualmann <metzpinguin@gmail.com> --- > Just a small excerpt, You have defective JPG files, although digiKam shouldn't > crash, but that will probably be the reason. > > digikam.dimg.jpeg: Invalid JPEG file structure: two SOI markers > digikam.dimg.jpeg: Unsupported marker type 0x50 > digikam.dimg.jpeg: Unsupported marker type 0x04 > > Maik >
If you have set the Debug environment variable, you still have to activate internal debugging under digiKam Settings-> Miscellaneous-> System. Then digiKam gets very chatty and we can see the names of the files that have errors. Maik
Created attachment 147637 [details] HP-LUTZ2_auszug.LOG Sehr geehrte Damen und Herren, vielen Dank für den Hinweis, dass ich unter Settings-> Miscellaneous-> System ein Protokoll einschalten kann. Doch wo finde ich dieses Protokoll? Ich habe gleichzeitig mit dem Tool dbgview64.exe eine Datei anlegen lassen. Diese Datei ist bis zum Absturz des Programms 584 Megabyte groß. Und ich weiß nicht, welcher Eintrag nun letztendlich zum Absturz führte. Und ich kann auch mit den diversen Zeilen wie "Standard Deviation for group of lines 0.689362" überhaupt nichts anfangen! Ist das nun wichtig für mich? Ist 0,1 besser als 0,9? Ich weiß es nicht. Oder solche Zeile "Detect if each part is motion blur"??? Ohne die Referenz auf die dazugehörige Datei ist diese Information für mich völlig irrelevant. Was soll das? Ebenso der Hinweis auf irgendwelche "Define Huffman Table" Einträge? Bitte sehen Sie es doch mal aus meiner Sichtweise: ich möchte meine Foto-Dateien sortieren. Ich möchte einfach auch Gesichter erkennen lassen. Und wenn es irgendwelche fehlerhaften Dateien geben sollte, die Ihren Kriterien nicht genügen, möchte ich einfach einen Hinweis auf diesen Dateinamen (vollständiger Dateiname inklusive Ordnerstruktur) erfahren. Vielleicht habe ich ja noch Dateien mit ähnlichen Inhalten in irgendwelchen anderen Ordnern, die aus Ihre Sicht nicht beschädigt sind? Zusammenfassung: 1. können Sie mir eine Liste der Dateien filtern, die mit dem Programm "DigiKam" als fehlerhaft erkannt werden, liefern? 2. welche Hinweise geben Sie mir, solche Dateien in ein Format zu konvertieren, das es mir ermöglicht, alle meine Fotos zu sortieren? Ich würde es begrüßen, wenn meine Bemerkungen in eine aktualisierte Version einfließen könnten. Mit freundlichen Grüßen Lutz Doering Dear Sir or Madam, Thank you for pointing out that I can turn on a log under Settings-> Miscellaneous-> System. But where can I find this protocol? I have created a file at the same time with the tool dbgview64.exe. This file is 584 megabyte until the program crashes. And I don't know which entry finally caused the crash. And I can't do anything with the lines like "Standard Deviation for group of lines 0.689362"! Is this important for me? Is 0.1 better than 0.9? I don't know. Or such line "Detect if each part is motion blur"??? Without the reference to the associated file, this information is completely irrelevant to me. What's the point? Also the reference to any "Define Huffman Table" entries? Please look at it from my point of view: I want to sort my photo files. I just want to have faces recognized as well. And if there should be any faulty files that don't meet your criteria, I just want to know a hint about this file name (full file name including folder structure). Maybe I still have files with similar content in any other folders that are not corrupted from your point of view? Summary: 1. can you provide me with a list of files filtered by the program "DigiKam" that are detected as corrupted? 2. what advice do you give me to convert such files into a format that will allow me to sort all my photos? I would appreciate if my comments could be included in an updated version. With kind regards Lutz Doering Translated with www.DeepL.com/Translator (free version) Am 18.03.2022 um 19:24 schrieb Maik Qualmann: > https://bugs.kde.org/show_bug.cgi?id=451637 > > --- Comment #6 from Maik Qualmann <metzpinguin@gmail.com> --- > If you have set the Debug environment variable, you still have to activate > internal debugging under digiKam Settings-> Miscellaneous-> System. Then > digiKam gets very chatty and we can see the names of the files that have > errors. > > Maik >
Please close my Ticket. I have actually no scrash, because i deinstalled the program, shut down and after restart install the actual Version 7.6.0 again. Mutually i found the solution by myself. Thank you for support. Am 18.03.2022 um 19:24 schrieb Maik Qualmann: > https://bugs.kde.org/show_bug.cgi?id=451637 > > --- Comment #6 from Maik Qualmann <metzpinguin@gmail.com> --- > If you have set the Debug environment variable, you still have to activate > internal debugging under digiKam Settings-> Miscellaneous-> System. Then > digiKam gets very chatty and we can see the names of the files that have > errors. > > Maik >