[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 caulier.gil...@gmail.com changed: What|Removed |Added Component|Versioning |Metadata-Versioning -- You are

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 --- Comment #15 from Gernot Hillier --- I fixed it manually now in the files as well as in the Digikam database "digikam4.db": 0. Shutdown digikam, backup digikam4.db and photos. 1. Scan all pictures using "exiftool -ImageUniqueId"

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 Gernot Hillier changed: What|Removed |Added CC||ger...@hillier.de ---

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 --- Comment #13 from Maik Qualmann --- Note: now re-read the metadata from the images to fix history. Maik -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Version Fixed

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 --- Comment #11 from gugs...@free.fr --- Hello, > There is a solution. You must enable the Option "Rescan file when files are > modified" in the metadata settings. Then use "touch" to call the relevant > files. The disadvantage is that the file date is

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 --- Comment #10 from Maik Qualmann --- There is a solution. You must enable the Option "Rescan file when files are modified" in the metadata settings. Then use "touch" to call the relevant files. The disadvantage is that the file

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 gugs...@free.fr changed: What|Removed |Added CC||gugs...@free.fr --- Comment #9 from

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 --- Comment #8 from Maik Qualmann --- Git commit c142f6b5c2a491db75253f75c331bdc2c4d48c0f by Maik Qualmann. Committed on 26/01/2017 at 11:37. Pushed by mqualmann into branch 'master'. blacklist Samsung cameras for

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 --- Comment #7 from Wolfgang Scheffner --- (In reply to Maik Qualmann from comment #5) > Created attachment 103626 [details] > uniqueID.patch > > Wolfgang can you test this patch? Re-reading the metadata should solve the >

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 --- Comment #6 from caulier.gil...@gmail.com --- Maik to comment #4 : yes, so far, a better solution at all. Why i don't think about it before (:=)))... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]

https://bugs.kde.org/show_bug.cgi?id=375483 Maik Qualmann changed: What|Removed |Added Summary|Wrong history on images |Wrong history on images