Pictures in Tableview not displayed in Thumbnailview

[Gurvan Huiban-6]

Hello Digikam Users,

A few days ago, the pictures taken with a specific device (a Samsung Cell
phone) stopped appearing in the Thumbnail view. Those pictures still appear in
the Table view.

A few details:

- I did not have the issue previously, so it is not an "incompatibility";

- It seems that only pictures from one device are impacted. The pictures from
my other devices are still visible in the thumbnail view;

- The files are still present physically on the hard drive and referenced in
the digikam4.db file;

- I search the mailing list, I could find another report for a similar issue
phenomenon (See https://mail.kde.org/pipermail/digikam-users/2015-January/
020638.html ), but I could not find how to solve the issue

- I am using Digikam 5.3.0 on Debian Stretch.

Did other people on the list encounter this issue? I do something wrong? If
not, is there a fix/workaround for the issue? Or does someone has a clue on
what I could do to ease the investigation?

Thank you

Best regards,

[Gilles Caulier-4]

This is probably the bugzilla entry for your problem :

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

Samsung make a mess in Exif metadata and do not follow the standard.

The patch was applied in source code. I'm not sure if it have been
introduced in 5.6.0, but i'm sure about 5.7.0. The Linux AppImage of
current implementation is here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

To solve your issue with the database (and image history tree
registered inside), it a little bit complex. In fact all Samsung image
have the same ID in database. So digiKam is lost.

The best way to check if problem is solved with 5.7.0 :

1/ use a new account, and run 5.7.0 with a fresh database.
2/ import samsung image in your collection and look if image still
here when scan is completed.

If it work, report your tests in the bugzilla file.

For your original database, we have now a maintenance tool in digiKam
to clean up the database tables. But i'm not sure if the Samsung case
is handled in this process. Another test case is to force the database
to re-read the file metadata. This must be talk in bugzilla as well.

Thanks in advance

Gilles Caulier

2017-08-24 7:29 GMT+02:00 Gurvan Huiban <[hidden email]>:

> Hello Digikam Users,
>
> A few days ago, the pictures taken with a specific device (a Samsung Cell
> phone) stopped appearing in the Thumbnail view. Those pictures still appear in
> the Table view.
>
> A few details:
>
> - I did not have the issue previously, so it is not an "incompatibility";
>
> - It seems that only pictures from one device are impacted. The pictures from
> my other devices are still visible in the thumbnail view;
>
> - The files are still present physically on the hard drive and referenced in
> the digikam4.db file;
>
> - I search the mailing list, I could find another report for a similar issue
> phenomenon (See https://mail.kde.org/pipermail/digikam-users/2015-January/
> 020638.html ), but I could not find how to solve the issue
>
> - I am using Digikam 5.3.0 on Debian Stretch.
>
> Did other people on the list encounter this issue? I do something wrong? If
> not, is there a fix/workaround for the issue? Or does someone has a clue on
> what I could do to ease the investigation?
>
> Thank you
>
> Best regards,
>
>

[Gurvan Huiban-6]

Hello, and thanks for your quick reply!

> This is probably the bugzilla entry for your problem :
>
> https://bugs.kde.org/show_bug.cgi?id=375483
>
> Samsung make a mess in Exif metadata and do not follow the standard.
[...]

> 1/ use a new account, and run 5.7.0 with a fresh database.
> 2/ import samsung image in your collection and look if image still
> here when scan is completed.
>
> If it work, report your tests in the bugzilla file.

I will do the test with the digikam version you provided me.

As the patch does not impact a lot of files, do you think the patch would apply
on the Digikam 5.3 version? So that I could easily re-generate a debian
package.

> For your original database, we have now a maintenance tool in digiKam
> to clean up the database tables. But i'm not sure if the Samsung case
> is handled in this process. Another test case is to force the database
> to re-read the file metadata. This must be talk in bugzilla as well.

I can also do the test with the patched software: re-reading the metadata, and
see if everything works.

I will report the results of those tests in the bugzilla. (I am not sure I
will have time to carry them out before the week-end, though).

> Thanks in advance

Thank you!

Gurvan

[Gilles Caulier-4]

yes, it's safe to apply the patch on 5.3.0, only if the patch work as
expected of course. This is why the feddback in bugzilla is important.

Gilles Caulier

2017-08-24 8:30 GMT+02:00 Gurvan Huiban <[hidden email]>:

> Hello, and thanks for your quick reply!
>
>> This is probably the bugzilla entry for your problem :
>>
>> https://bugs.kde.org/show_bug.cgi?id=375483
>>
>> Samsung make a mess in Exif metadata and do not follow the standard.
> [...]
>
>> 1/ use a new account, and run 5.7.0 with a fresh database.
>> 2/ import samsung image in your collection and look if image still
>> here when scan is completed.
>>
>> If it work, report your tests in the bugzilla file.
>
> I will do the test with the digikam version you provided me.
>
> As the patch does not impact a lot of files, do you think the patch would apply
> on the Digikam 5.3 version? So that I could easily re-generate a debian
> package.
>
>> For your original database, we have now a maintenance tool in digiKam
>> to clean up the database tables. But i'm not sure if the Samsung case
>> is handled in this process. Another test case is to force the database
>> to re-read the file metadata. This must be talk in bugzilla as well.
>
> I can also do the test with the patched software: re-reading the metadata, and
> see if everything works.
>
> I will report the results of those tests in the bugzilla. (I am not sure I
> will have time to carry them out before the week-end, though).
>
>> Thanks in advance
>
> Thank you!
>
> Gurvan

[Gurvan Huiban-6]

Hello,

I made some tests with Digikam 5.7.0

1) With a Fresh account/database: I imported pictures taken with the Samsung
cellular, and then updated them (crop/rotation/etc.); everyrhing worked as
expected: The pictures remained visible/reachable in the  Thumbnail view

2) With my "old" digikam database, which already contains pictures unreachable
via Thumbnail view: re-reading metadata from the picture did not solve
anything (e.g. The pictures remained visible in Table view, but not in
Thumbnail view)

3) With my "old" digikam database, which already contains pictures unreachable
via Thumbnail view: Deleting the Samsung pictures and re-importing them made
them visible/reachable again via Thumbnail view.

It seems that the patch proposed solves the issue for new (or newly imported)
files, but does not solve anything for "already imported" files (even by re-
reading the metadata).

I added the comments below in the BugZilla.

This leads us to the second question: How can I repari my already existing
database?

As a sidenote: my system runs Debian Stable, with Digikam 5.3. Is there any
risk in running the Digikam 5.7 Appimage file that I downloaded instead of the
one provided by Debian? (Compilation against libs that are from different
version, making the app sometime unstable, or stuff like that).

Thank you.
Best regards,
Gurvan