I'm not sure it this is a bug or a feature, what I know it happens already for ages, at least version 3.x. Every time I change time zone - e.g. from UTC to Central European time - on my system digikam starts rescanning my image collection even though neither the database nor the image folder have been touched or changed. This is a bit of a nuisance since with big image collections it can take a while. BTW, both my image folder as well as the database are on an external USB harddrive. Reproducible: Always Steps to Reproduce: 1. change time zone 2. connect harddrive 3. start digikam - you better do it from a terminal to see what digikam -> see this bug https://bugs.kde.org/show_bug.cgi?id=360474 Actual Results: Digikam scans the whole collection again. Expected Results: Digikam should just start in the normal way it does without changing time zone. I'm not sure when I recognized this behaviour the first time, but I think after changing from version 2.x to 3.x.
If the time zone is changed, the modification date of files is changed. Therefore digiKam starts a rescan. date -r test.jpg => Fr 20. Nov 22:41:35 CET 2015 timedatectl set-timezone America/New_York date -r test.jpg => Fr 20. Nov 16:41:35 EST 2015 timedatectl set-timezone Europe/Berlin date -r test.jpg => Fr 20. Nov 22:41:35 CET 2015 I see at the moment is no easy way to change this. Date / time store in DB as UTC and only users visible entries convert to local date / time? Maik
(In reply to Maik Qualmann from comment #1) > If the time zone is changed, the modification date of files is changed. > Therefore digiKam starts a rescan. Thanks for the explanation. Already guessed that this was the reason. But honestly, modification time does not really change. It only looks differently. > I see at the moment is no easy way to change this. Date / time store in DB > as UTC and only users visible entries convert to local date / time? Maybe that could help. Or an algorithm, that detects that modification time not really has changed. Knut
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
No clue if this bug still prevails. I just stopped changing time zone and only change the time displayed by the clock.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
No clue, if this still happens in the way I had described it here. I simply do not change time zone any more. It's always set do UTC and I only change the time displayed.
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!