digiKam 2.5.0: missing photos

[Aleck Mueller]

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?
--
Aleck

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Simon Cropper-3]

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?
>

Can you open the files with any other viewer or editor?

Can you upload one or all files somewhere so others can test?
Alternatively, see if the files are recognized and rendered on any other
machine you have nearby. maybe the files are corrupt and that is why
they are not imported.

--
Cheers Simon

    Simon Cropper - Open Content Creator

    Free and Open Source Software Workflow Guides
    ------------------------------------------------------------
    Introduction               http://www.fossworkflowguides.com
    GIS Packages           http://www.fossworkflowguides.com/gis
    bash / Python    http://www.fossworkflowguides.com/scripting
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[tosca]

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

--

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

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Aleck Mueller]

В Ср., 28/08/2013 в 09:25 +1000, Simon Cropper пишет:
> Can you open the files with any other viewer or editor?
For instance, Eye of GNOME Image Viewer shows the file without any
problem.
--
Aleck

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Aleck Mueller]

В Ср., 28/08/2013 в 02:05 +0200, Marie-Noëlle Augendre пишет:

> 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.
>

It seems like that.
When I purged digiKam package I deleted files digikam4.db and
thumbnails-digikam.db from the database directory afterwards; it is
strange enough that they were there after purging. Then I installed the
package again and before launching digiKam file digikam4.db had appeared
in the database directory! After launching digiKam the initial setup
assistant did not appeared but a simple setup dialogue window was
appeared instead.
--
Aleck

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Aleck Mueller]

В Ср., 28/08/2013 в 09:25 +1000, Simon Cropper пишет:
> Can you upload one or all files somewhere so others can test?
Yes.
But the file is 2.3 MB and I am not sure this size is convenient for the
maillist; anyhow let me know if it is required.
--
Aleck

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

there is a file at ~/.kde4/share/config/digikamrc, which store all
digiKam config. First Assistant only appear if this file do not exist
(typically if digiKAm have never be run on the system).

Remove this file to show assistant.

Gilles Caulier

2013/8/28 Aleck Mueller <[hidden email]>:

> В Ср., 28/08/2013 в 02:05 +0200, Marie-Noëlle Augendre пишет:
>> 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.
>>
> It seems like that.
> When I purged digiKam package I deleted files digikam4.db and
> thumbnails-digikam.db from the database directory afterwards; it is
> strange enough that they were there after purging. Then I installed the
> package again and before launching digiKam file digikam4.db had appeared
> in the database directory! After launching digiKam the initial setup
> assistant did not appeared but a simple setup dialogue window was
> appeared instead.
> --
> Aleck
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Aleck Mueller]

В Ср., 28/08/2013 в 02:05 +0200, Marie-Noëlle Augendre пишет:
> Now there are some maintenance tools included in Digikam interface,
> that might help to fix that issue.
I have only found the possibility to change the database
SQLite -> MySQL in the program setup menu, but if the state of SQLite is
corrupted I do not expect the one of MySQL will be correct. Are the
maintenance tools you mentioned applied to my version of digiKam?
Changing the version within the limits of installed OS is problematic
for me due to the lack of competence.
--
Aleck

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Aleck Mueller]

В Ср., 28/08/2013 в 07:09 +0200, Gilles Caulier пишет:
> there is a file at ~/.kde4/share/config/digikamrc, which store all
> digiKam config. First Assistant only appear if this file do not exist
> (typically if digiKAm have never be run on the system).
>
> Remove this file to show assistant.
Thank you very much for the advice.
--
Aleck

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Aleck Mueller]

В Ср., 28/08/2013 в 07:09 +0200, Gilles Caulier пишет:

> there is a file at ~/.kde4/share/config/digikamrc, which store all
> digiKam config. First Assistant only appear if this file do not exist
> (typically if digiKAm have never be run on the system).
>
> Remove this file to show assistant.
>
> Gilles Caulier
>
> 2013/8/28 Aleck Mueller <[hidden email]>:
> > В Ср., 28/08/2013 в 02:05 +0200, Marie-Noëlle Augendre пишет:
> >> 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.
> >>
> > It seems like that.
> > When I purged digiKam package I deleted files digikam4.db and
> > thumbnails-digikam.db from the database directory afterwards; it is
> > strange enough that they were there after purging. Then I installed the
> > package again and before launching digiKam file digikam4.db had appeared
> > in the database directory! After launching digiKam the initial setup
> > assistant did not appeared but a simple setup dialogue window was
> > appeared instead.
> > --
> > Aleck
> >
> > _______________________________________________
> > Digikam-users mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-users
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

I have removed digikam4.db, thumbnails-digikam.db and
~/.kde/share/config/digikamrc (since directory ~/.kde4 does not exist),
reinstalled digiKam and got strange result: after setup with First
Assistant and scanning collection digiKam shows in the album 1202
pictures again WITH the test picture there! Therefore some other one
should disappear this time instead. And again:
$ ls -1 album-name | wc -l
1205

I can't think what's wrong.
By the way /home is mounted on a partition with file system EXT4 and
option data=journal.

--
Aleck

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Simon Cropper-3]

On 28/08/13 14:53, Aleck Mueller wrote:
> В Ср., 28/08/2013 в 09:25 +1000, Simon Cropper пишет:
>> Can you upload one or all files somewhere so others can test?
> Yes.
> But the file is 2.3 MB and I am not sure this size is convenient for the
> maillist; anyhow let me know if it is required.
>

It would be advantageous to make this file available as it would allow
others to try the file.

If we can see and manipulate the file then the issue is with the setup.

One less thing to consider.

P.S. The file is not a constraint, at least from my point of view. Don't
post it to the list -- use a public file server like MegaFileUpload,
FreeUploadSite or similar. If the image is personal and you don't want
it on the internet then send it directly to me or encrypt the file and
send the password directly to me. Once I check the file I will delete it
from my system.

--
Cheers Simon

    Simon Cropper - Open Content Creator

    Free and Open Source Software Workflow Guides
    ------------------------------------------------------------
    Introduction               http://www.fossworkflowguides.com
    GIS Packages           http://www.fossworkflowguides.com/gis
    bash / Python    http://www.fossworkflowguides.com/scripting
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Simon Cropper]

Aleck,

Thanks for sending the file.

It appears the file you sent has corrupted metadata.

I can't see it in digiKam or any other package that reads metadata.

If I delete the image's metadata then I see it in digiKam.

I corrected the problem with my system by extracting the metadata from the file using exiv2, deleting the data from the file then inseting the data back again.

I could then see the file in digiKam and it appeared to have all the basic metadata I would expect.

On 28/08/13 15:12, Aleck Mueller wrote:

В Ср., 28/08/2013 в 02:05 +0200, Marie-Noëlle Augendre пишет:

Now there are some maintenance tools included in Digikam interface,
that might help to fix that issue.

I have only found the possibility to change the database
SQLite -> MySQL in the program setup menu, but if the state of SQLite is
corrupted I do not expect the one of MySQL will be correct. Are the
maintenance tools you mentioned applied to my version of digiKam?
Changing the version within the limits of installed OS is problematic
for me due to the lack of competence.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[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

--

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

_______________________________________________
Digikam-users mailing list
[hidden email]
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.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Aleck Mueller]

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

--

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

_______________________________________________
Digikam-users mailing list
[hidden email]
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.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Aleck Mueller]

Unfortunately the problem has suddenly arisen again (with chosen MySQL)
:-( .
Since it is serious by itself now I have to consider some another
program instead of digiKam.
08.01.2014 08:24, Aleck Mueller пишет:
> I have found a workaround for the problem: :-)
>
> 1) choosing MySQL instead of SQLite;

--
Aleck

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[tosca]

Why don't you upgrade Digikam?
 Stable version is now 3.5 (4.0 in release candidate, I think) so you're way behind. Many bugs have been fixed, many new functionalities have appeared since 2.5.

Marie-Noëlle

2014/1/13 Aleck Mueller <[hidden email]>

Unfortunately the problem has suddenly arisen again (with chosen MySQL) :-( .
Since it is serious by itself now I have to consider some another program instead of digiKam.
08.01.2014 08:24, Aleck Mueller пишет:

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

1) choosing MySQL instead of SQLite;

--
Aleck

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

--

Retrouvez mon portfolio et mes activités dans ma galerie personnelle, mes reportages sur Jingoo

Et bien sûr la page Photographe en Cévennes sur FB, et mon compte Twitter.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2014/1/13 Marie-Noëlle Augendre <[hidden email]>

Why don't you upgrade Digikam?
 Stable version is now 3.5 (4.0 in release candidate, I think)

4.0.0 will be released as beta2 soon. 4.0.0 is planed for may or june. More than 120 bugs are now closed, and the goal is to do more and more. It's a long time to stabilize code.

 

Gilles Caulier

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[tosca]

My mistake. I read something about 4.0 and didn't pay attention enough as it wasn't stable version; so it was beta and not RC.

Anyway, as he's still in 2.5, it seems he has some upgrading leeway even before 4.0 is out. :-)

Marie-Noëlle

2014/1/13 Gilles Caulier <[hidden email]>

2014/1/13 Marie-Noëlle Augendre <[hidden email]>

Why don't you upgrade Digikam?
 Stable version is now 3.5 (4.0 in release candidate, I think)

4.0.0 will be released as beta2 soon. 4.0.0 is planed for may or june. More than 120 bugs are now closed, and the goal is to do more and more. It's a long time to stabilize code.

 

Gilles Caulier

--

Retrouvez mon portfolio et mes activités dans ma galerie personnelle, mes reportages sur Jingoo

Et bien sûr la page Photographe en Cévennes sur FB, et mon compte Twitter.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

4.0.0 Road map is here :

http://community.kde.org/Digikam/GSoC2013#Roadmap_and_Releases_Plan_including_all_GSoC-2013_works

Gilles Caulier

2014/1/13 Marie-Noëlle Augendre <[hidden email]>

My mistake. I read something about 4.0 and didn't pay attention enough as it wasn't stable version; so it was beta and not RC.

Anyway, as he's still in 2.5, it seems he has some upgrading leeway even before 4.0 is out. :-)

Marie-Noëlle

2014/1/13 Gilles Caulier <[hidden email]>

2014/1/13 Marie-Noëlle Augendre <[hidden email]>

Why don't you upgrade Digikam?
 Stable version is now 3.5 (4.0 in release candidate, I think)

4.0.0 will be released as beta2 soon. 4.0.0 is planed for may or june. More than 120 bugs are now closed, and the goal is to do more and more. It's a long time to stabilize code.

 

Gilles Caulier

--

Retrouvez mon portfolio et mes activités dans ma galerie personnelle, mes reportages sur Jingoo

Et bien sûr la page Photographe en Cévennes sur FB, et mon compte Twitter.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Aleck Mueller]

Because I use LTS (Mint KDE 13) with its standard repositories and not
an expert in Linux system administration.
13.01.2014 23:01, Marie-Noëlle Augendre пишет:
> Why don't you upgrade Digikam?

--
Aleck

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users