**SUMMARY** digiKam 8.8.0 crashes on Windows 10 during startup when loading media after splash screen. **STEPS TO REPRODUCE** 1. Install digiKam 8.8.0 on Windows 10 (fresh install or upgrade from previous version). 2. Launch digiKam. 3. Observe splash screen, then crash occurs when application attempts to load media library. **OBSERVED RESULT** - Splash screen appears. - Application crashes immediately when loading media. - No usable main window is displayed. - Issue persists across multiple reinstallations and attempts with different digiKam versions. **EXPECTED RESULT** - digiKam should start successfully and load the media library without crashing. - Main window should be accessible for browsing and managing photos. **SOFTWARE/OS VERSIONS** - **Windows:** Windows 10 (64-bit, fully updated) - **macOS:** N/A - **Linux/KDE Plasma:** N/A - **KDE Plasma Version:** N/A - **KDE Frameworks Version:** N/A - **Qt Version:** (bundled with digiKam installer, unknown exact version) **ADDITIONAL INFORMATION** - Tried uninstalling and reinstalling multiple times. - Tested with different digiKam versions (including 8.8.0 and earlier). - Same crash occurs consistently. - No custom configuration applied; default settings used. - A backtrace with debug symbols can be provided if needed.
Please create a DebugView log, as described here for Windows: https://www.digikam.org/contribute/#windows-host Maik
Created attachment 186689 [details] DebugView logs attached
You have plenty of : digikam.general: Could not find parent with url: "/Rosie's iPhone/DCIM" for: "/Rosie's iPhone/DCIM/202210_c" Sounds like something is missing in your collection. At end we have messages generated outside digiKam before the crash: 00000631 18.09413528 [10624] ECM Get clsid failed: 800401f3 00000632 18.09423447 [10624] ECM Initialize::NONE 00000633 18.10832977 [10624] ECM Current temperature is:6500 00000634 18.11477280 [10624] ECM Current temperature is:6500 00000635 18.12152672 [10624] ECM Current temperature is:6500 ECM = Engine Color Management. So there is a problem with a color profile on your computer. Perhaps a file uses to render coloer on your monitor, or a color space defined in a file as metadata. This is what Mistral AI give as analyze results based on your log: //--- Log Analysis ECM Get clsid failed: 800401f3 This error code (800401f3) typically indicates an issue with accessing or registering a CLSID (Class ID) in the Windows Registry. Possible causes: A required component for color management (e.g., an ICC profile or system library) is missing or improperly installed. digiKam or its dependencies lack permissions to access the registry or system files. Conflicts with other color management software (e.g., Adobe Color Management, DisplayCAL). ECM Initialize::NONE Indicates the color management engine failed to initialize, likely due to the previous error. ECM Current temperature is:6500 This is a normal message showing the default color temperature (6500K). It is not related to the crash but confirms the color engine attempted to start. Troubleshooting Steps 1. Check digiKam Dependencies Default ICC profiles for the display (Windows usually installs these automatically, but corruption is possible). If digiKam was installed via an installer, try repairing or reinstalling it. 2. Permissions and Windows Registry Run digiKam as Administrator (right-click > "Run as administrator") to check if the issue persists. This can bypass permission issues. If the problem disappears in admin mode, check the user permissions for registry keys related to color management or ICC profiles. 3. Conflicts with Other Color Management Software Temporarily disable other color management software (e.g., Adobe Color Settings, DisplayCAL, or f.lux) and restart digiKam. Check if the issue occurs after installing another color management tool. 4. Reset ICC Profiles Go to Windows Settings > System > Display > Advanced display settings > Display adapter properties. Ensure the default color profile is selected (usually "sRGB" or a manufacturer-provided profile). If a custom profile is selected, try resetting it to the default. 5. Clean the Registry (Advanced) If comfortable with the Windows Registry, check for keys related to color management: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID Look for entries related to LCMS2 or QtColor. Warning: Back up the registry before making any changes. 6. Update Graphics Drivers Outdated or corrupted graphics drivers can interfere with color management. Update your GPU drivers (NVIDIA, AMD, or Intel). 7. Test with Another Windows User Create a new Windows user account and test digiKam from there. If the issue doesn’t occur, the current user profile may be corrupted. Quick Action Summary Reinstall digiKam. Use the official installer to repair or reinstall.Run as AdminTest if the issue is permission-related.Disable Color Management SoftwareCheck for conflicts with Adobe, DisplayCAL, etc.Reset ICC ProfileSwitch to the default profile (sRGB). Update Graphics Drivers. Ensure NVIDIA/AMD/Intel drivers are up to date. Question: Has the user recently installed or updated color management software, or changed Windows display settings? If so, this could be the direct cause. Do you have more details about their system configuration? //---
is it possible to remove the collections from loading? Even after reinstalling there seems to be residual files that is reading an old configurations and the folders that is causing the errors
(In reply to vincentywt from comment #4) > is it possible to remove the collections from loading? Even after > reinstalling there seems to be residual files that is reading an old > configurations and the folders that is causing the errors It didn't work even running under Administrator either by the way
The problem with the missing parent album isn't the collection itself, but the database. Please rename the digiKam4.db file and let digiKam recreate it. Maik
Vincent, Do you seen the last Maik comment ? Gilles Caulier