[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 Marvin changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Marvin --- Hi Gilles, Thank you for following up. And apologies for my disappearance from this issue. What happened was that I kept updating stable and beta versions, then started tracing the errors and deleting images that I believe were causing problems, but that took quite some time with the many decades of pictures that I've collected. At some point, when I start digiKam, I'd get an error: - You have insufficient privileges on the database. Following privileges are not assigned to you: ALTER TABLE Check your privileges on the database and restart digiKam. - The app still starts, and I can hit the OK button, then check for latest version, and initiate an upgrade. Installer would do uninstall of current version, then installs the latest, with no visible errors. As I never got through a full scan, I just decided to clean up completely, install the latest daily build 2023-10-14 I could find, create new database and let it scan all subdirectories. I'm back to this PC after several hours and I see that digiKam is still working, it has "No active process" and would like to think that the issue is gone. Thank you for your help! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 --- Comment #9 from caulier.gil...@gmail.com --- @Marvin, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 --- Comment #8 from caulier.gil...@gmail.com --- >From your DebugView session, these messages : [29904] digikam.general: Trying to get thumbnail from Embedded preview with Exiv2 for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory Image, entry 0x0111: Strip 0 is outside of the data area; ignored. [29904] [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory SubImage1 has an unexpected next pointer; ignored. [29904] [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory SubImage1, entry 0x0001 has unknown Exif (TIFF) type 0; setting type size 1. [29904] [29904] digikam.metaengine: Exiv2 ( 3 ) : Offset of directory SubImage1, entry 0x0001 is out of bounds: Offset = 0x0005829d; truncating the entry [29904] [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory SubImage1, entry 0x0001 has unknown Exif (TIFF) type 0; setting type size 1. [29904] [29904] digikam.metaengine: Exiv2 ( 3 ) : Offset of directory SubImage1, entry 0x0001 is out of bounds: Offset = 0x00038827; truncating the entry [29904] [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory SubImage1, entry 0x0001 has unknown Exif (TIFF) type 0; setting type size 1. [29904] [29904] digikam.metaengine: Exiv2 ( 3 ) : Offset of directory SubImage1, entry 0x0001 is out of bounds: Offset = 0x00079000; truncating the entry [29904] [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory SubImage1, entry 0x0004 has unknown Exif (TIFF) type 0; setting type size 1. [29904] [29904] digikam.metaengine: Exiv2 ( 3 ) : Directory SubImage1, entry 0x0004 has invalid size 808596016*1; skipping entry. [29904] [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory SubImage1, entry 0x0014 has unknown Exif (TIFF) type 0; setting type size 1. [29904] [29904] digikam.metaengine: Exiv2 ( 3 ) : Offset of directory SubImage1, entry 0x0014 is out of bounds: Offset = 0x00029004; truncating the entry ... are warnings from Exiv2 library i charge to extract metadata from file. some chunk exceeds the limit from the TIFF norm, and are truncated. That all. CR2 files are TIFF with private extensions from Canon, this explain that. These message are typical more problematic : [29904] digikam.rawengine: LibRaw: loadEmbeddedPreview from "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.rawengine: LibRaw: failed to run open_file: Unsupported file format or not RAW file [29904] digikam.rawengine: Failed to load embedded RAW preview [29904] digikam.general: Trying to get thumbnail from half preview with libraw for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.rawengine: Try to use reduced RAW picture extraction [29904] digikam.rawengine: LibRaw: failed to run open_file: Unsupported file format or not RAW file These come from Libraw engine used to handle RAW file contents. CR2 are supported since a while, so the file information must be taken without exception. I would to double check this file on my computer to see if i can reproduce this error here. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 --- Comment #7 from caulier.gil...@gmail.com --- Hi Marvin, >What are the exact instructions for v8.1-beta on Win11. The instructions at >https://www.digikam.org/contribute/ under Windows Host state >"If digiKam start properly, go to Setup/Misc/System dialog page..." >I guess those are moved around and called something different now? Maybe >Settings/Configure digiKam/Miscellaneous/System? >"... and turn on the option to generate debug traces." >That isn't there, either. I assume it's "Enable internal debug logging"? I fixed all typo in this page and add a new section to guide with QtCreator to catch the debugger backtrace. Visit again https://www.digikam.org/contribute/ Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 Marvin changed: What|Removed |Added Version|8.0.0 |8.1.0 --- Comment #6 from Marvin --- (In reply to caulier.gilles from comment #5) > Well the only way to catch the bug is to clean up the database and rescan > from scratch to try to reproduce the bug. > > the most simpler way can be to create a new user and start digiKam to > repopulate a database. As the collection of files is huge, the best way will > be to import step by step small part of files with debugview in background > to catch the problematic files. When identified, you can share the files > using cloud to investigate here and found the bug. > > Tip: on the new account, start digiKam without any files imported, go to > setup/misc/system and enable debug trace for debugview. After that, start > debugview, take a care that debug traces from digiKam are visible, and start > to import files in your database, until a crash appears. > > Best > > Gilles Caulier Hi Gilles, I did add my pic-RAW folder. I had removed it when I saw lots of exiftool.exe piled up in Win11 the Task Manager and it started crashing again. I also changed to the weekly betas and selected the Debug option. Now, after a few more start/crash/kill exiftool processes/start/crash/etc... it again completed to 100%... but it still crashed while I had left it in the background and wasn't interacting with digiKam for a bit. What are the exact instructions for v8.1-beta on Win11. The instructions at https://www.digikam.org/contribute/ under Windows Host state "If digiKam start properly, go to Setup/Misc/System dialog page..." I guess those are moved around and called something different now? Maybe Settings/Configure digiKam/Miscellaneous/System? "... and turn on the option to generate debug traces." That isn't there, either. I assume it's "Enable internal debug logging"? Also, when I exit digiKam, it appears to close normally. Yet, there are still many exiftool.exe that remain running. Assuming my guesses above were somewhat correct, I still don't get a log file under C:\Users\\AppData\Local\digikam What I do see in DebugView are errors like those but can't spot something that'd crash the app, as it goes to the next RAW file fine. And I had no RAW files initially when I reported the bug. --- [29904] digikam.metaengine: Check ExifTool availability: true [29904] digikam.metaengine: ExifTool "Load Chunks" "-TagsFromFile D:\\pics-RAW\\RAW\\2013\\IMG_7139 (1).CR2 -all:all -o -.exv" [29904] digikam.database: Scanning took 135 ms [29904] digikam.dbengine: Database is locked. Waited 0 [29904] digikam.metaengine: ExifToolProcess::readOutput(): ExifTool command completed [29904] digikam.metaengine: ExifTool complete command for action "Load Chunks" with elasped time (ms): 25 [29904] digikam.metaengine: EXV chunk size: 6855 [29904] digikam.metaengine: ExifTool parsed command for action "Load Chunks" 1 properties decoded [29904] digikam.metaengine: ExifTool complete "Load Chunks" for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.metaengine: Metadata chunk loaded with ExifTool [29904] digikam.metaengine: Loading metadata with "ExifTool" backend from "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.general: Trying to get thumbnail from "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" ( "image" ) [29904] digikam.general: Trying to get thumbnail with Exiv2 for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.general: Trying to get thumbnail with DImg preview for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.general: Trying to get thumbnail from Embedded preview with libraw for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.rawengine: LibRaw: loadEmbeddedPreview from "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.rawengine: LibRaw: failed to run open_file: Unsupported file format or not RAW file [29904] digikam.rawengine: Failed to load embedded RAW preview [29904] digikam.general: Trying to get thumbnail from half preview with libraw for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.rawengine: Try to use reduced RAW picture extraction [29904] digikam.rawengine: LibRaw: failed to run open_file: Unsupported file format or not RAW file [29904] digikam.general: Trying to get thumbnail from Embedded preview with Exiv2 for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory Image, entry 0x0111: Strip 0 is outside of the data area; ignored. [29904] [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory SubImage1 has an unexpected next pointer; ignored. [29904] [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory SubImage1, entry 0x0001 has unknown Exif (TIFF) type 0; setting type size 1. [29904] [29904] digikam.metaengine: Exiv2 ( 3 ) : Offset of directory SubImage1, entry 0x0001 is out of bounds: Offset = 0x000
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 --- Comment #5 from caulier.gil...@gmail.com --- Well the only way to catch the bug is to clean up the database and rescan from scratch to try to reproduce the bug. the most simpler way can be to create a new user and start digiKam to repopulate a database. As the collection of files is huge, the best way will be to import step by step small part of files with debugview in background to catch the problematic files. When identified, you can share the files using cloud to investigate here and found the bug. Tip: on the new account, start digiKam without any files imported, go to setup/misc/system and enable debug trace for debugview. After that, start debugview, take a care that debug traces from digiKam are visible, and start to import files in your database, until a crash appears. Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 --- Comment #4 from Marvin --- (In reply to caulier.gilles from comment #3) > How many files do you have in your collection ? > > I don't know why crash course do not handle the exception. > > The debugview running in background will indicate where in scan process the > crash appear, typically which file is the cause of the exception. > > the HEIF format can be a source of dysfunction. > > Best > > Gilles Caulier Hi Gilles, d:\pics contains 126,437 Files, 919 Folders. After a couple of more days of crashes while scanning, killing all digiKam processes, and restarting, the "Find new items" now got to 100%!!! I'm going to reinstall the normal, not -debug, version. Unless you want me to try something so we can find the bug and devs will fix it for other users. Thanks, Marv -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 --- Comment #3 from caulier.gil...@gmail.com --- How many files do you have in your collection ? I don't know why crash course do not handle the exception. The debugview running in background will indicate where in scan process the crash appear, typically which file is the cause of the exception. the HEIF format can be a source of dysfunction. Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 --- Comment #2 from Marvin --- (In reply to caulier.gilles from comment #1) > Hi Marvin, > > Please give us more details: > > - The database type that you use. > - The king of file format that you manage on your collection. > - The program trace captured with debugview and the crash course captured > with DrMinGW (see details here : https://www.digikam.org/contribute/) > > Thanks in advance > > Gilles Caulier Hi Gilles, I did install the -debug version and it keeps crashing. I was hoping to get a .log file or something easily readable to crawl and try to see what breaks. There are no .log files under C:\Users\\AppData\Local\digikam, just \cache and \facesengine. It's an old Picasa set of subfolders with pics taken by various Nexus and Pixel phones, both jpg and raw, also some I got from iphone users. It looks like it's crashing while scanning. If I kill all the digiKam processes and start it again the "Find new items" bar seems to be able to progress by another percent or so. I'm at 96% after many many mny restarts. The install was done with just clicking Next so internal SQLite, I guess. Apart from installing Sysinternals and DebugView, is there something simple I can review? Thanks, Marv -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Hi Marvin, Please give us more details: - The database type that you use. - The king of file format that you manage on your collection. - The program trace captured with debugview and the crash course captured with DrMinGW (see details here : https://www.digikam.org/contribute/) Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
