Bug 508464

Summary: Album marked as not available although it is available
Product: [Applications] digikam Reporter: Jan van Bekkum <Jan.vanBekkum>
Component: Database-AlbumsAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 8.7.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In: 8.8.0
Sentry Crash Report:

Description Jan van Bekkum 2025-08-19 11:56:20 UTC 
SUMMARY
One album suddenly was marked as not available, although its folder can be opened in explorer. Creating a new album of the same folder works correctly. Other albums opened correctly.

STEPS TO REPRODUCE
1. Start digiKam
2. Try to open album
3. 

OBSERVED RESULT
Error message that storage location is not available

EXPECTED RESULT
Opening of album

SOFTWARE/OS VERSIONS
Windows:  10
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 caulier.gilles 2025-08-19 12:25:06 UTC 
What's the kind of collection do you use for this album ? local, removable, network ?
Comment 2 Jan van Bekkum 2025-08-19 12:33:10 UTC 
Local network (NAS)
Comment 3 Maik Qualmann 2025-08-19 13:48:16 UTC 
By "album," do you mean a standalone digiKam collection? Then you should see a red X icon on the collection's root album.
If you mean an album from an existing collection, it could be due to a file path that's too long. Please install digiKam-8.8.0, which now supports long file paths.

If it's a collection, the partition UUID has probably changed, or you deleted the digiKam UUID file in the .dtrash folder used to identify the collection. Then simply run the update function for the corresponding collection in the digiKam collection settings.

Maik
Comment 4 Jan van Bekkum 2025-08-20 06:47:09 UTC 
Thanks for your reply. It concerns a collection. I thought that I had gone through the steps that you recommend, but appparently I made an error. I tried again and now it worked. Sorry for reporting abug that wasn't a bug.