[Digikam-users] digiKam 2.5.0: missing photos

Aleck Mueller myuller.aleck at ya.ru
Wed Jan 8 02:24:55 GMT 2014


I have found a workaround for the problem: :-)

1) choosing MySQL instead of SQLite;

2) with such choice a side effect has arisen: Album Library Path cannot 
be set up because of national symbols in root-album name (in spite of 
UTF-8 system locale) - I had to create root-album Pictures for it in my 
home directory (national symbols in sub-album names are acceptable).

Hence it appears that missing photos themselves are not a cause of the 
problem (SQLite?).

Software:
OS - Linux Mint 13 KDE (LTS)
digikam    4:2.5.0-1ubuntu2

libqt4-sql-sqlite:amd64 (4.8.1-0ubuntu4.5)

libsqlite3-0    3.7.9-2ubuntu1.1
mysql-server    5.5.34-0ubuntu0.12.04.1

-- 
Aleck

28.10.2013 12:20, Aleck Mueller ?????:
>
> 28.08.2013 06:05, Marie-Noëlle Augendre ?????:
>>
>>
>>     On 27/08/13 20:05, Aleck Mueller wrote:
>>
>>         Hello
>>
>>         On Ubuntu 12.04 LTS I am going to use digiKam instead of
>>         default Shotwell,
>>         so I installed package digiKam and set up the root album at
>>         first run
>>         with a collection of photos already in it. Checking the
>>         result of first
>>         scanning of the collection I have found that 3 photos of 1205
>>         are missed
>>         in one of subalbums although ls shows they are there. I chose
>>         one of them
>>         for testing:
>>         1) moved it to another directory, launched digiKam and
>>         imported it
>>         again - without result;
>>         2) purged and then installed package digiKam again - the same;
>>         3) launched digiKam in terminal window - there were several
>>         messages
>>         complaining about *.mov files in albums but this one is jpg-file;
>>         4) looked at the metadata of the chosen file by means of
>>         console program
>>         exif - they looked like normal.
>>
>>         What is wrong?
>>
>>
>>
>>
>> There use to be a problem like that sometimes ago: some pictures 
>> could never be recognized by Digikam whatever you do, and though they 
>> were perfectly OK with other programs.
>> I don't know if the problem still exists, but it was due to wrong 
>> records left in the database and - at that time - the only 
>> possibility was to remove them manually, or start with a new DB from 
>> scratch.
>> Now there are some maintenance tools included in Digikam interface, 
>> that might help to fix that issue.
>>
>> Marie-Noëlle
>>
>>
>>
>> -- 
>> <http://fr.ulule.com/aigoual-aubrac/>
>>
>> /*De l'AIgoual à l'Aubrac*, un voyage photographique en Cévennes et 
>> Lozère/
>> Un livre à offrir ou à s'offrir, en souscription jusqu'au 31 août 2013.
>> Cliquer sur l'image ci-dessus ou ce lien pour en savoir plus 
>> <http://fr.ulule.com/aigoual-aubrac/>
>>
>>
>> _______________________________________________
>> Digikam-users mailing list
>> Digikam-users at kde.org
>> https://mail.kde.org/mailman/listinfo/digikam-users
> This message is a try to resume the discussion.
> Now on another OS - Linux Mint 13 KDE - but with the same version of 
> digiKam the problem has arisen again. Unfortunately, "start with a new 
> DB from scratch" does not work.
>
> In due time Simon Cropper experimented kindly with one such file 
> provided by me. He found out the procedure:
>
> exiv2 extract p1020398.jpg
> exiv2 delete p1020398.jpg
> exiv2 insert p1020398.jpg
>
> gets the image appeared in digiKam and he suspected the file is 
> somehow corrupted.
>
> But command "cmp" shows about this procedure that the initial and 
> final versions of the file are identical. Moreover "Reread Metadata" 
> (the last item of the Album Menu marked with curved green arrow) 
> results in disappearance the image again so it seems to me the problem 
> concerned with database interaction.
>
> The point of the problem is unstable behaviour of the program intended 
> for professional use. I have about 0.2% of such files but absolutely 
> uncertain about which new ones will fill up this collection.
>
> If anybody is going to test this problem I am ready to send such file 
> (there are three about 2 MB each) directly to his/her email.
> -- 
> Aleck
>
>
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users

-- 
Aleck

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20140108/f67b877d/attachment.html>


More information about the Digikam-users mailing list