SUMMARY I used DigiKam in the past and it was working fine (I had version 7.6). It's been 2 years maybe so I installed the update this morning. Tried with 8.4, 8.5 and 8.6. They all crash. STEPS TO REPRODUCE 1. Open DigiKam 2. 3. OBSERVED RESULT It crash after a couple seconds. With 8.6 I get this error in EventViewer : Faulting application name: digikam.exe, version: 8.6.0.0, time stamp: 0x6791dbc2 Faulting module name: digikamgui.dll, version: 0.0.0.0, time stamp: 0x6791dbb3 Same thing with 8.5 and Qt6: Faulting application name: digikam.exe, version: 8.5.0.0, time stamp: 0x67376ddd Faulting module name: digikamgui.dll, version: 0.0.0.0, time stamp: 0x67376d66 Exception code: 0xc0000005 Fault offset: 0x0000000000210b70 Faulting process ID: 0x6f84 Faulting application start time: 0x01db70dbfb808c1f Faulting application path: C:\Program Files\digiKam\digikam.exe Faulting module path: C:\Program Files\digiKam\digikamgui.dll Report ID: bd2f98bb-8568-47e8-b008-c4d1892a7ba0 Faulting package full name: Faulting package-relative application ID: With 8.5 and Qt5: Faulting application name: digikam.exe, version: 8.5.0.0, time stamp: 0x67376a24 Faulting module name: Qt5Core.dll, version: 5.15.14.0, time stamp: 0x667b2748 With 7.6: Faulting application name: digikam.exe, version: 7.6.0.0, time stamp: 0x00000000 Faulting module name: KERNELBASE.dll, version: 10.0.19041.5369, time stamp: 0xc3ec0adc Exception code: 0xc0000602 SOFTWARE/OS VERSIONS Windows: 10 Qt Version: I tried with the Qt5 and Qt6 versions
Here digiKam-8.6.0 runs on 3 machines (Windows 10/11) without problems. Can you please create a DebugView log to see approximately where it crashes, as described here: https://www.digikam.org/contribute/#windows-host Maik
(In reply to Maik Qualmann from comment #1) > Here digiKam-8.6.0 runs on 3 machines (Windows 10/11) without problems. > Can you please create a DebugView log to see approximately where it crashes, > as described here: > > https://www.digikam.org/contribute/#windows-host > > Maik First time I tried to run with the DebugView (64bits), it took forever and did open fine. Now, I don't know what I am doing differently but I can't make it open. Here is the last part of the log concerning a file that I renamed : [29444] digikam.metaengine: Loading metadata with "Exiv2" backend from "D:/Pictures/***.MP.jpg" [29444] digikam.dimg: "D:/Pictures/***.MP.jpg" : "JPEG" file identified [29444] digikam.dimg.jpeg: Start of Image ( 1 ) [29444] digikam.dimg.jpeg: Miscellaneous marker 0xe1, length 47987 ( 1 ) [29444] digikam.dimg.jpeg: JFIF APP0 marker: version 1.02, density 1x1 0 ( 1 ) [29444] digikam.dimg.jpeg: Miscellaneous marker 0xe2, length 610 ( 1 ) [29444] digikam.dimg.jpeg: Miscellaneous marker 0xe1, length 1492 ( 1 ) [29444] digikam.dimg.jpeg: Miscellaneous marker 0xe1, length 44841 ( 1 ) [29444] digikam.dimg.jpeg: Miscellaneous marker 0xe2, length 86 ( 1 ) [29444] digikam.dimg.jpeg: Define Quantization Table 0 precision 0 ( 1 ) [29444] digikam.dimg.jpeg: Define Quantization Table 1 precision 0 ( 1 ) [29444] digikam.dimg.jpeg: Start Of Frame 0xc0: width=3024, height=4032, components=3 ( 1 ) [29444] digikam.dimg.jpeg: Component 1: 2hx2v q=0 ( 1 ) [29444] digikam.dimg.jpeg: Component 2: 1hx1v q=1 ( 1 ) [29444] digikam.dimg.jpeg: Component 3: 1hx1v q=1 ( 1 ) [29444] digikam.dimg.jpeg: Define Huffman Table 0x00 ( 1 ) [29444] digikam.dimg.jpeg: 0 1 5 1 1 1 1 1 ( 2 ) [29444] digikam.dimg.jpeg: 1 0 0 0 0 0 0 0 ( 2 ) [29444] digikam.dimg.jpeg: Define Huffman Table 0x10 ( 1 ) [29444] digikam.dimg.jpeg: 0 2 1 3 3 2 4 3 ( 2 ) [29444] digikam.dimg.jpeg: 5 5 4 4 0 0 1 125 ( 2 ) [29444] digikam.dimg.jpeg: Define Huffman Table 0x01 ( 1 ) [29444] digikam.dimg.jpeg: 0 3 1 1 1 1 1 1 ( 2 ) [29444] digikam.dimg.jpeg: 1 1 1 0 0 0 0 0 ( 2 ) [29444] digikam.dimg.jpeg: Define Huffman Table 0x11 ( 1 ) [29444] digikam.dimg.jpeg: 0 2 1 2 4 4 3 4 ( 2 ) [29444] digikam.dimg.jpeg: 7 5 4 4 0 1 2 119 ( 2 ) [29444] digikam.dimg.jpeg: Start Of Scan: 3 components ( 1 ) [29444] digikam.dimg.jpeg: Component 1: dc=0 ac=0 ( 1 ) [29444] digikam.dimg.jpeg: Component 2: dc=1 ac=1 ( 1 ) [29444] digikam.dimg.jpeg: Component 3: dc=1 ac=1 ( 1 ) [29444] digikam.dimg.jpeg: Ss=0, Se=63, Ah=0, Al=0 ( 1 ) [29444] digikam.database: Adding new item "D:/Pictures/***.MP.jpg" [29444] digikam.database: Recognized "D:/Pictures/***.MP.jpg" as identical to item 12796 [29444] digikam.database: Scanning took 4 ms After that, nothing, application window disappear. I have around 8000 pictures, and did a huge reorganization of folders and file names, is it the problem ?
oh, and after a while, this appeared in the log : [27916] SCEN_SETFOCUS [27916] SystemUpdate [27916] IDC_PREV/NEXT_DOC [27916] SystemUpdate
Hi, digiKam 8.6.0 is just released: https://www.digikam.org/news/2025-03-15-8.6.0_release_announcement/ Problem still exists with this version? Thanks in advance Gilles Caulier
(In reply to caulier.gilles from comment #4) > Hi, > > digiKam 8.6.0 is just released: > > https://www.digikam.org/news/2025-03-15-8.6.0_release_announcement/ > > Problem still exists with this version? > > Thanks in advance > > Gilles Caulier I have similar problem with 8.6.0, 8.5.0 was no problem. with the new version it crahes after showing the splash screen. I have tried to start digikam also after removing digikamrc. This allows me to go through the startup setup, but after the setup it crashes. Not sure if this is right information you need: [17192] qt.svg: QSvgHandler: Image filename is empty [17192] qt.svg: QSvgHandler: Image filename is empty [17192] qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Win::WinStorageAccess::repairRequested(QString) [17192] qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Win::WinStorageAccess::repairDone(Solid::ErrorType, QVariant, QString) [17192] qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Win::WinStorageAccess::repairRequested(QString) [17192] qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Win::WinStorageAccess::repairDone(Solid::ErrorType, QVariant, QString) [17192] kf.config.core: KConfigIni: In file C:/Users/xx/AppData/Roaming/digikam/digikamstaterc, line 39: Invalid escape sequence: «\.» [17192] kf.config.core: KConfigIni: In file C:/Users/xx/AppData/Roaming/digikam/digikamstaterc, line 39: Invalid escape sequence: «\I» [17192] kf.config.core: KConfigIni: In file C:/Users/xx/AppData/Roaming/digikam/digikamstaterc, line 40: Invalid escape sequence: «\P» [17192] kf.config.core: KConfigIni: In file C:/Users/xx/AppData/Roaming/digikam/digikamstaterc, line 41: Invalid escape sequence: «\S» [17192] kf.config.core: KConfigIni: In file C:/Users/xx/AppData/Roaming/digikam/digikamstaterc, line 62: Invalid escape sequence: «\D» [17192] kf.config.core: KConfigIni: In file C:/Users/xx/AppData/Roaming/digikam/digikamstaterc, line 81: Invalid escape sequence: «\D» [17192] qt.svg: QSvgHandler: Image filename is empty [17192] qt.svg: QSvgHandler: Image filename is empty [17192] qt.svg: QSvgHandler: Image filename is empty [17192] qt.svg: QSvgHandler: Image filename is empty [17192] digikam.facedb: Face database: cannot process schema initialization I have also tried the snapshot of 2.7.0 same issue.
I dont know how to edit a comment. Need to add i use Windows 11 and correct the digiKam version number in last line it shall be 8.7.0 not 2.7.0.
If you're using SQLite as your database, delete the "recognition.db" file, which will then be recreated. For digiKam-8.6.0, the training data for the faces needs to be rebuilt anyway. Maik
(In reply to Maik Qualmann from comment #7) > If you're using SQLite as your database, delete the "recognition.db" file, > which will then be recreated. For digiKam-8.6.0, the training data for the > faces needs to be rebuilt anyway. > > Maik Thanks a lot this solved the problem (removing the "recognition.db" file). Best regards, Dennis