[Digikam-devel] [Bug 236730] Collection path is interpreted differently

Marcel Wiesweg marcel.wiesweg at gmx.de
Tue May 18 16:19:54 BST 2010


https://bugs.kde.org/show_bug.cgi?id=236730





--- Comment #6 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-18 17:19:49 ---

> I have 2 disk partitions home and root.
> 9aea5987... is sda3
> f9ac797c... is crypt_LUKS of sda3 which is /home/USERNAME

Then the old database was perfectly all right, because f9ac + /media/pictures
is on your system obviously /home/USERNAME/media/pictures
Something must have changed on your system (broken HAL / Solid) so that this
partition is no longer visible to digikam.

> 8d105535... is sda1 the root partition.
> 


> 
> That is what I did.
> 
> Now the question from all of this. Digikam does not have a way of editing the 
> collections only adding new ones and removing old ones. If digikam had this 
> feature there would not be a need to dabble with the DB to fix this issue. This 
> would be of particular interest for less experienced users.

All normal use cases should be covered. The occasional bug report here is
usually caused by broken platform libraries (HAL / Solid etc.)

> 
> Further more there seems to be dependance between image metadata (comments, 
> rating & etc) and the album. If an album were to break (say recovering from
> dead 
> disk) there does not seem to be a trivial way of rebuilding this short of 
> manually hacking away at the Album roots table. This seems like a great way for 
> a user to loose important data. It would be nice for digikam on creation of a 
> new album to check for image hashes and compare them to the existing ones (in 
> DB) and relink meta-data based on hashes.

Of course, digikam checks the recorded hash and copies all metadata when it
finds an identical file.
Unfortunately, we rely on libexiv2 to get hashes over metadata, and the data
libexiv2 returned to us changed in the past, so the hashes got different.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Digikam-devel mailing list