https://bugs.kde.org/show_bug.cgi?id=517354
--- Comment #8 from [email protected] --- Created attachment 190570 --> https://bugs.kde.org/attachment.cgi?id=190570&action=edit Changed face database name face database name was incorrect. Changed the name in settings, which led to digikam hanging / becoming unresponsive. Closed and re-opened. Same results as previously: only 2 albums visible. MariaDB [digikam]> select * from Albums; returns 32722 rows in set (0.035 sec) Rows look very similar to MariaDB [digikam]> select * from Albums limit 0,3; +----+-----------+--------------+------------+---------+------------+------+---------------------+ | id | albumRoot | relativePath | date | caption | collection | icon | modificationDate | +----+-----------+--------------+------------+---------+------------+------+---------------------+ | 1 | 0 | 1-/ | 2003-04-19 | NULL | NULL | NULL | 2025-06-26 07:51:00 | | 2 | 0 | 1-/3d scans | 2022-04-05 | NULL | NULL | NULL | 2022-04-05 10:10:48 | | 3 | 0 | 1-/4chan | 2026-01-24 | NULL | NULL | NULL | 2026-01-27 21:34:17 | +----+-----------+--------------+------------+---------+------------+------+---------------------+ but found some seeming doubles MariaDB [digikam]> select * from Albums where "id" < 32720 and id > 32718; +-------+-----------+----------------------------+------------+---------+------------+------+---------------------+ | id | albumRoot | relativePath | date | caption | collection | icon | modificationDate | +-------+-----------+----------------------------+------------+---------+------------+------+---------------------+ | 32719 | 0 | 1-/Events/Sinterklaas 2025 | 2026-01-30 | NULL | NULL | NULL | 2026-01-30 16:19:00 | | 32720 | 1 | / | 2025-06-26 | NULL | NULL | NULL | NULL | | 32721 | 1 | /3d scans | 2022-04-05 | NULL | NULL | NULL | 2022-04-05 10:10:48 | | 32722 | 1 | /4chan | 2026-02-06 | NULL | NULL | NULL | NULL | +-------+-----------+----------------------------+------------+---------+------------+------+---------------------+ 4 rows in set, 1 warning (0.000 sec) MariaDB [digikam]> select * from Albums where relativePath like "1-/%"; results in 32719 rows in set (0.038 sec) and MariaDB [digikam]> select * from Albums where relativePath like "/%"; +-------+-----------+--------------+------------+---------+------------+------+---------------------+ | id | albumRoot | relativePath | date | caption | collection | icon | modificationDate | +-------+-----------+--------------+------------+---------+------------+------+---------------------+ | 32720 | 1 | / | 2025-06-26 | NULL | NULL | NULL | NULL | | 32721 | 1 | /3d scans | 2022-04-05 | NULL | NULL | NULL | 2022-04-05 10:10:48 | | 32722 | 1 | /4chan | 2026-02-06 | NULL | NULL | NULL | NULL | +-------+-----------+--------------+------------+---------+------------+------+---------------------+ 3 rows in set (0.018 sec) are also the only albums that show up in my Albums list. Considering: - When I restarted digikam the second time after installation of 9.0.0 it asked me to enter a collection again - I added the same network share - I have scan for new files on startup set (which I cancel pretty much as soon as I started up the last few times) it looks like somehow digikam set albumRoot to 0 and relativePath to 1-/% and found the 3 with albumRoot 1 and relativePath /% entries whilst scanning. Do you recommend me deleting the last 3 entries and setting albumRoot to 1 for all that is 0, as well as replacing the relativePath 1-% to %? It won't solve the mystery of why that was changed though - there were no network outages with the NAS whilst I upgraded (.exe installer) from 8.8.0. -- You are receiving this mail because: You are watching all bug changes.
