Digikam Won't Open - Corrupted Data File
Maik Qualmann
metzpinguin at gmail.com
Fri Nov 29 20:34:54 GMT 2024
If you cannot delete the digiKam4.db with Explorer after restarting, you may
not have rights to this network collection. But if the progress bar in
Explorer stops, I suspect a file system/hard drive error on your NAS.
Maik
Am Freitag, 29. November 2024, 17:44:41 Mitteleuropäische Normalzeit schrieb
Marty Ducote:
> After using it for months, I can't open digikam at all. After fighting
> with it for several hours, I've narrowed it down to a corrupted db file,
> possibly two.. I've tried to delete the files and let digikam recreate
> them, but they will not be deleted.
>
> Here's where I am:
>
> * Windows 11 on an administrator account
> * digikam 8.4.0
> * Photo files are stored in multiple folders and sub folders within a
> parent folder (named All Photos) on an external networked hard
> drive. The database files (digikam4.db and digikam4.db-journal) are
> in the parent folder. All Photos was created by me. It's not a
> Pictures folder that Windows created.
> * File explorer shows that the digikam4.db file is about 10 MB and the
> journal file is 0 KB
>
> What I've Tried:
>
> * File explorer, right clicking and choosing Delete. The "running
> actions" window will run indefinitely showing 0% progress.
> * Same step, using run as administrator. Same result.
> * Uninstalling and reinstalling digikam multiple times, including
> numerous reboots. When I tried to uninstall a couple of times, it
> told me it could not uninstall because digikam was already running,
> even though I had just rebooted the computer and had not started the
> program.
> * I booted into Safe Mode with Networking but my external drive was
> not available.
> * Trying to delete it using the command prompt window
> * Installing the program on a different computer with identical access
> to the external hard drive, but since the corrupted file is in the
> primary photo folder, digikam wouldn't start on that computer, either.
>
> My first computer was a DOS machine, so I'm pretty comfortable in
> Command Prompt. I am less familiar with Windows Terminal, so may need
> more specific help if that's part of the path.
>
> The program did exactly what I needed it to do, albeit a little slowly.
> Any ideas what I can do to get digikam back?
>
> Marty
More information about the Digikam-users
mailing list