Bug 501603 - Queue empty after crash
Summary: Queue empty after crash
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-Metadata (other bugs)
Version First Reported In: 8.7.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-16 20:51 UTC by Andy
Modified: 2025-12-09 19:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy 2025-03-16 20:51:21 UTC
Hi!
digiKam crashed. I'm not sure why yet.
But that's another topic. "Use Lazy Synchronization" is active. There were about 60 files in the queue. Due to the crash, the changes weren't written to the file. After starting digiKam, the queue is empty.
Is there a way to still execute the last changes?

Regards
Andy
Comment 1 Maik Qualmann 2025-03-17 06:59:15 UTC
The crash is the problem. The queue isn't saved, and it's not intended.

Maik
Comment 2 Andy 2025-03-17 07:48:01 UTC
Hello,
All right! Then I'm no longer allowed to use this option.
I liked working with it because it was a bit faster in my network environment. With about 300-400 entries in the queue, I let them process and made myself a coffee.

Regards
Andy
Comment 3 caulier.gilles 2025-04-11 17:34:07 UTC
Hi,

The digiKam 8.7.0 pre-release for Windows have been rebuild from scratch today with many improvements and updates. Please test with this version to see if the problem is reproducible.

Link to download: https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier
Comment 4 Andy 2025-04-11 20:00:22 UTC
Hello,

I confirmed four faces of one person. They were displayed in the queue. I force-quit digiKam in Task Manager. The changes weren't written to the files. The changes are in the database.

When I restart digiKam, the queue is empty.

Regards
Andy
Comment 5 caulier.gilles 2025-04-11 20:09:47 UTC
So to conclude ?
Comment 6 caulier.gilles 2025-12-09 07:03:05 UTC
Andy,

When crash happen, we need a debugger backtrace. Please look at instructions here :

https://www.digikam.org/contribute/#windows-host-1

Gilles Caulier
Comment 7 Andy 2025-12-09 19:02:17 UTC
Hi Gilles, 
the crash wasn't the problem. The program has been running without issues for months. The problem was with the queue that appears in case of a crash or connection loss to the database, and the necessary program restart. The queue is then empty. Subsequent writing to the files was no longer possible.

Andy