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: [hidden email] Reporter: [hidden email] 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. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
https://bugs.kde.org/show_bug.cgi?id=329976
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #1 from Gilles Caulier <[hidden email]> --- Pressing F5 in when album do not fix the issue ? Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|general |Thumbnails -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
--- Comment #2 from Nicofo <[hidden email]> --- (In reply to comment #1) > Pressing F5 in when album do not fix the issue ? No, it doesn't. Only 'reread metadata from image' works. You can easily reproduce this bug, and it is even not necessary to open / close digikam as I mentioned above: 0) create a folder with "picture 1.jpg" "picture 2.jpg" "picture 3.jpg" etc... ; to simply view an effect of this bug, say that all the pictures are in landscape (orientation=top-left) and "picture 17.jpg" is in portrait (orientation='left-bottom') 1) open digikam and view that album -> all OK 2) delete one picture (say "picture 15.jpg") 3) rename all the pictures (so that "picture 16" takes the place of deleted "picture 15" etc...) (batch renaming program, for instance multiple renaming from dolphin) 4) see what happens in digikam ... PS: you have attached this bug to the "Thumbnails" component: for me it's not really the thumbnails themselves: it's the fact that digikam associates to the new "picture 16.jpg" information from the old "picture 16.jpg" (now "picture 15.jpg") etc. The thumbnails are correct, I mean they are related to the correct picture, but are eventually not correctly orientated (I can add that if you click on the thumbnail to see the picture 'full screen', it is in the same way badly orientated. Once again, only 'reread metadata from image' works). -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Thumbnails |Database -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
--- Comment #3 from Marcel Wiesweg <[hidden email]> --- Digikam sees the filename as a relatively strong property of a file. Assume you edit your file with gimp. Afterwards, the file contents and file size will have changed, only the filename remains. For certain operations done from outside digikam, the explicit "Reread metadata from file" is necessary. If digikam is running during the rename operation, with working Linux notification services, the renaming should be recognize, I would be interested if it works. If you rename from within digikam, it must work as well. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
--- Comment #4 from Nicofo <[hidden email]> --- (In reply to comment #3) > If digikam is running during the rename operation, with working Linux > notification services, the renaming should be recognize, I would be > interested if it works. Yes and no: If I rename outside digikam while digikam is running (or not: no impact), digikam sees that files have changed since their names are automatically updated. However, the metadata are not automatically reread, hence strange behaviors as explained above. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Digikam does not update its |SCAN : Digikam does not |DB after picture renaming, |update its DB after picture |resulting in multiple |renaming, resulting in |confusions |multiple confusions -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|SCAN : Digikam does not |SCAN : digiKam does not |update its DB after picture |update its DB after picture |renaming, resulting in |renaming, resulting in |multiple confusions |multiple confusions -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
--- Comment #5 from Gilles Caulier <[hidden email]> --- *** Bug 329390 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|SCAN : digiKam does not |SCAN : digiKam does not |update its DB after picture |update database after |renaming, resulting in |picture renaming |multiple confusions | -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Database |Database-Scan -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #6 from [hidden email] --- Are you able to reproduce the issue with 5.0.0 version? In a new folder, I have a list of pictures: - picture 01.jpg - picture 02.jpg ... - picture 5.jpg 1) digiKam reads the images fine. 2) Outside digikam (digikam is closed), I delete 'picture 3.jpg' and rename the next pictures: 'picture 4.jpg' becomes 'picture 3.jpg' 'picture 5.jpg' becomes 'picture 4.jpg' 3) When I open digiKam again, these images are correctly identified, with their respective properties.... -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Version Fixed In| |5.1.0 --- Comment #7 from [hidden email] --- This issue is not reproducible with 5.0.0 Feel free to reopen if you still face this and provide necessary updates, if any. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
Nicofo <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|FIXED |--- Version|3.5.0 |5.0.0 --- Comment #8 from Nicofo <[hidden email]> --- Hello I reopen the bug because it is still valid for me. I made the same manipulation, and there are still problems. I have 14 files 'Test 01.jpg ... Test 14.jpg' 1) Eveything is fine in digikam. See 1st screenshot [1] with details about 'Test 10.jpg'. See for instance that this picture is geolocalised (map icon) and camera is Panasonic. 2) I delete 'Test 07.jpg' and rename Test 08 -> Test 07 etc... (outside digikam) 3) Now in digikam, NOK: see 2d screenshot [2] with details about 'Test 09.jpg' (which was 'Test 10' before, so same picture as above). See that this picture is no more geolocalised (map icon) and camera is Canon. These are the properties of picture 08 (old 09), so all the picture properties are 'shifted'. Note: comparing [1] and [2], you see immediately that there is a problem with the map icon (top-right side of thumbs) AND with the date (from 'Test 08', there is now a 'Modification Date') [1] http://nicofo.tuxfamily.org/tmp/Digikam-1-Before.jpg [2] http://nicofo.tuxfamily.org/tmp/Digikam-2-After.jpg -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
--- Comment #9 from [hidden email] --- Which dtatabse type you use ? sqlite or mysql ? Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
--- Comment #10 from Nicofo <[hidden email]> --- the default one: sqlite (I just freshly installed digikam 5.0 in Fedora 24, using default settings) -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
--- Comment #11 from [hidden email] --- What's about this file using digiKam AppImage bundle 5.4.0 pre release given at this url : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
--- Comment #12 from Nicofo <[hidden email]> --- Hi Gilles, I tested again with DK 5.3. There is progress, this problem is nearly solved, but not with the Tags. I made the same test as in comment #8 I have no problem anymore related to the properties of the pictures (geolocalisation icon is OK, 'modified date' is ok, ...) BUT well with the tags. The tags are not correct anymore. And the behaviour is different depending if I make the renaming while DK is running or not. Say that picture 3 has a tag 'TAG'. If I delete picture 2 and rename the other (picture 3 becomes 2 ...): -> I expect that picture 2 has now the 'TAG', BUT: - if DK is running: now picture 2 and 3 have 'TAG' - if DK is not running: after restart of DK, the tags are 'shifted' to the neighbour picture: now picture 3 has the 'TAG' -> so in both situations it is not good. (hope the explanation is clear ;) ) -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by Nicofo
https://bugs.kde.org/show_bug.cgi?id=329976
Nicofo <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|5.0.0 |5.3.0 -- You are receiving this mail because: You are the assignee for the bug. |
Free forum by Nabble | Edit this page |