Bug 480242 - AlbumRoot not resolved
Summary: AlbumRoot not resolved
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Albums (show other bugs)
Version: 8.2.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-23 19:14 UTC by timmib
Modified: 2024-01-23 20:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 8.3.0
Sentry Crash Report:


Attachments
Screenshot (40.83 KB, image/png)
2024-01-23 19:18 UTC, timmib
Details
Terminal output (45.99 KB, text/x-log)
2024-01-23 19:32 UTC, timmib
Details

Note You need to log in before you can comment on or make changes to this bug.
Description timmib 2024-01-23 19:14:03 UTC
SUMMARY
***
Using the 8.2.0 appimage the image cannot be opened and the path is displayed as "???/..." in the file-properties on the right.
Using the 8.1.0 appimage everything is fine. 
Using 8.2.0 in Windows is also working fine!
I am using a remote mariadb. AlbumRoots Table looks good.
***


STEPS TO REPRODUCE
1. Open Digikam 8.2.0 appimage
2. Try to open a image by doubleclick for example
3. Check the path in the file-properties

OBSERVED RESULT
"Der Speicherort dieses Bildes ist zurzeit nicht verfügbar"

EXPECTED RESULT
Image opens like using the 8.1.0 appimage

SOFTWARE/OS VERSIONS
Windows: 11
macOS: -
Linux/KDE Plasma: Ubuntu 22.04.3 LTS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 timmib 2024-01-23 19:18:00 UTC
Created attachment 165167 [details]
Screenshot

Evidence :o)
Comment 2 Maik Qualmann 2024-01-23 19:21:18 UTC
Start the AppImage in a terminal and first set the Qt Debug variable:

export QT_LOGGING_RULES="digikam*=true"
./digiKam-8.3.0-XXXX.appimage

Post the output in the terminal.

Maik
Comment 3 timmib 2024-01-23 19:32:25 UTC
Created attachment 165168 [details]
Terminal output

Issue already apeared before i added P:\ for windows.
Comment 4 Maik Qualmann 2024-01-23 19:44:29 UTC
We introduced a new file UUID in digiKam-8.2.0. Your file UUID in the DB starts with 8e78dc98..., in your collection starts with 53e0302c..., so unequal. How this could have happened is not clear to me at the moment. Simply delete the file in your collection "/mnt/Foto/.dtrash/digikam.uuid". The file is automatically recreated and the AlbumRoot entry is adjusted.

Maik
Comment 5 timmib 2024-01-23 19:45:32 UTC
I recently moved the collection to another drive....
Comment 6 timmib 2024-01-23 19:48:02 UTC
Deleteing the file "/mnt/Foto/.dtrash/digikam.uuid" solved it!

Thanks a lot for the hyperfast support!