[Digikam-devel] [digikam] [Bug 329976] New: Digikam does not update its DB after picture renaming, resulting in multiple confusions

[Nicofo]

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

            Bug ID: 329976
           Summary: Digikam does not update its DB after picture renaming,
                    resulting in multiple confusions
    Classification: Unclassified
           Product: digikam
           Version: 3.5.0
          Platform: Fedora RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: digikam-devel at kde.org
          Reporter: nicofo at tuxfamily.org

I have a list of pictures:
- picture 01.jpg
- picture 02.jpg
...
- picture 20.jpg

1) I read them with digikam -> no problem (for instance: orientation of the
pictures is correct)

2) Outside digikam (digikam is closed), I delete 'picture 15.jpg' and rename
the next pictures:
'picture 16.jpg' becomes 'picture 15.jpg'
'picture 17.jpg' becomes 'picture 16.jpg'
...
'picture 20.jpg' becomes 'picture 19.jpg'

3) I open digikam again: as a result, the pictures from n°15 are not correctly
displayed: picture 15 (i.e. old 16) is displayed according to the properties of
the old picture 15, idem for the others.
For instance -> if orientation of old_15 was 'right top' and orientation of
new_15 (i.e. old_16) is 'top left' -> digikam displays the new_15 in a wrong
orientation
Other example: digikam timestamp of new_15 is the one of old_15
Etc...

So the internal database of digikam is not updated in this situation.

Remarks:
a) In the 'image' menu -> 'reread metadata from image' fixes the problem. But
this should be transparent for the user.
b) If metadata are not reread, several mistakes can be done by the user/digikam
subsequently. For instance, if you 'Auto rotate/flip using exif information' ->
the wrong pictures will be rotated.

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.