https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #43 from maison <bugzi...@kgb.ovh> --- This bug is not only about geo‐location. I’ve just discovered a few files that happened to have no CreateDate field (which forced digiKam to use the DateTimeCreated field). I updated them through the -csv=csv file option from exiftool. Then I rescanned the folder in digiKam. Surprise (or not so much anymore): these jpegs are still presented at the wrong date in the Date selection tree and keep that date underneath in Digikam. So I tried the brutal method again: I created a new digiKam profile. Surprise (or not): these files now have the date they deserve in digiKam. As a side note, these files are named nothing fancy, like 24.jpg. No extra Unicode. Maybe more importantly I should add, my exiftool pre‐made commands bear the flags -overwrite_original -P , which shouldn’t be a problem for digiKam as it used to rescan the files correctly on demand in the past. -- You are receiving this mail because: You are watching all bug changes.
