SUMMARY I cannot add any collections from folders located on a secondary HDD. STEPS TO REPRODUCE 1. Add collection in configure box 2. Select folder on secondary drive 3. Click ok OBSERVED RESULT Error: It was not possible to add a collection for the following path: F:\Pictures EXPECTED RESULT F:\Pictures added as collection SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
Install Microsoft's DebugView, set the Debug System environment variable and give us the log when trying to add the collection. Description here: https://www.digikam.org/contribute/ Otherwise we will not be able to reproduce it, a possible cause would be that your drive was or is a system drive and contained a Winsows installation. A general problem is not known, I often add drives when testing the Windows version. Maik
Created attachment 141046 [details] Log
This drive previously held the windows installation.
It looks as if digiKam is now using drive C: instead of drive F: digikam.database: Folder does not exist or is not readable: "C:/Pictures/[Date Sorted]" Unfortunately, the volume UUID on Windows are often the same if hard drives are not formatted. Either you change the volume UUID of drive F: with an appropriate tool. Or add drive F: as a network collection. Maik
*** This bug has been marked as a duplicate of bug 398831 ***
I just had this problem with my Lubuntu PC. digikam has been acting strangely since I added a new hard disk to the computer. Most of the time it displays a message to the effect that the disk containing the collection is not available. Wrong, it is an internal SATA hard disk. Today I decided to delete the Mysql Internal database and start again, hoping that digikam would obey its configuration and only read digikam tags from my photos and ignore all of the ancient Microsoft, ACDSee etc. tags. When I started the 7.8.0 appimage from the desktop digikam said that it couldn't add the collection and closed. I opened Terminal, set the QT debugging rule and started the appimage. Everything is working, BUT I still have all of the data I was trying to lose. Regards Steve
When you replace an internal hard drive, it also has a new UUID. You then have to press the update button (circle icon) for the entry in the collection settings and go through the dialogs (in principle without changing anything if the path has remained the same). The UUID is then updated again in the database. Maik
That is what I do most days. Occasionally digikam doesn’t say that it cannot find my Photo folder. N.B. This wasn’t a replacement drive. I used to have my photos on a USB Hard Disk, then decided to copy everything to an internal drive. This was then partitioned and formatted under Linux, before all the data on the USB disk was transferred to it. Today I become fed up with removing old flat tags, so I renamed the MySQL database folder. That is when this error occurred. Starting digikam from terminal fixed the problem (next time I run digikam I will double-click the appimage icon, to check whether the fix is permanent). Unfortunately I don’t know how to capture the debug data in terminal. I tried selecting the output with the mouse; right-clicking; selecting Copy Selection to clipboard. When I tried pasting it into Featherpad, there was nothing to paste.
Fixed with 398831