| Summary: | digikam doesn't find DB anymore after change of settings | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Kristian <kde-bugs> |
| Component: | Setup-Metadata | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/-/commit/dcb3949d95ada9184da50aef5b88488985497c9e | Version Fixed/Implemented In: | 8.4.0 |
| Sentry Crash Report: | |||
| Attachments: |
digikam startup log (after bug happened)
Screenshots |
||
|
Description
Kristian
2024-03-24 17:43:41 UTC
You mean that after changing metadata settings, the sqlite database file have been dropped from your disk. This is very strange, i never seen this behavior in the past... The file "digikam4.db" was gone, but a file called "digikam4.db-backup-2024-03-24T18:04:56" was there instead. You have to rename the backup file to digikam4.db. Then you don't have to scan everything again. Maik That's what I did, digkam started the scanning automatically. This means you have set a new location for your database, otherwise it would use the file. Check the database settings to see if the path is still correct. Maik It is still the same and I did not touch it. Created attachment 167711 [details]
digikam startup log (after bug happened)
Please see attached log: digikam.database: Creating new Location "/$USER/Bilder/Fotos" uuid "volumeid:?uuid=27ea6369-b602-469f-b7e7-XXXXXXXXXXX&fileuuid=40d34373-bac4-4760-bfca-XXXXXXXXXXX" Might it be some issue with the UUID? I migrated to a new laptop several weeks ago. However, it's strange that it appears now. Git commit dcb3949d95ada9184da50aef5b88488985497c9e by Maik Qualmann. Committed on 24/03/2024 at 18:56. Pushed by mqualmann into branch 'master'. fix logic if the WAL mode changes, only check for changes to the database FIXED-IN: 8.4.0 M +1 -1 NEWS M +3 -4 core/libs/album/manager/albummanager_database.cpp https://invent.kde.org/graphics/digikam/-/commit/dcb3949d95ada9184da50aef5b88488985497c9e Your log shows that after switching to another laptop, your collection settings are no longer completely valid, the UUID of the partition has changed. We have recently started using a new file UUID in the collection, which is why the collection can also be found after the change. You should still update the collections. Use the "update" function in the digikam settings under Collections (round circle icon) behind the collection. Normally you can simply adopt all the settings in the dialogs that arise. Maik OK, I did this, but digikam is still continuing to perform a full scan for new entries. I assume it's save to continue to use the backup database or is there anything I need to check? Certainly the UUID of the disk partition is not the same than original disk. In the Setup Collection, you have a button to adjust the UUID of a path managed by the database . https://docs.digikam.org/en/setup_application/collections_settings.html Gilles Caulier I finally found some time to have another look and I can easily reproduce the bug with a backup. As per the discussion, it is because of the changed UUID and should be fixed in the next version, but did you also investigate why it happens after checking the two boxes in the settings? If needed, I can provide more info. I also made a PDF with some screenshots. Created attachment 169579 [details]
Screenshots
|