Version: 0.8.0-beta2 (using KDE KDE 3.4.2) Installed from: Compiled From Sources OS: Linux After importing a Photo1.jpg in an Album which contains already a (different) Photo1.jpg (with the menu Album->Import->Add Images...), its thumbnail is not updated immediately and if Photo1.jpg was used 'As Album thumbnail' then its Album thumbnail is not updated immediately too.
I can confirm this on digiKam 0.8.1. This could be confusing, user clicking on the overwrite button can think that images wasn't overwriten, because thumbnail wasn't updated.
Confirming for 0.9.3svn. Have to manually refresh or reenter album to replace old thumbnail.
Mik, Are you the same problem with 0.9.3 or current svn implementation ? Gilles Caulier
Confirming for 0.9.4svn (ver. 793314) After importing image with the same name: a) thumbnail is properly shown only after reentering of album b) if this image was selected for album thumbnail this is visible only after restart of digiKam
Thanks mik, Marcel, it's another problem with KDirWatch or an AlbumManager race condition ? Gilles Caulier
I still can confirm this, thumbnails are not updated when importing images with an already used filename. Switching to another album and back will update the thumbnails in album icon view, but not the album thumbnail itself. After restarting digiKam the album thumbnail is updated, too. Andi
Andi, This still valid with 0.10.0 ? Gilles
Yes... just checked it.
The thumbnail is now updated when importing into an album, but if the image that is overwritten was the album thumbnail, you still need to restart digiKam to see an effect.
It still valid with 2.4.0 release ? Gilles Caulier
Andi, can you check if this entry still valid with current implemntation from git/master ? Gilles Caulier
If a photo with same name is imported into an album, its thumbnail is updated immediately. This problem appears to be solved. But if it is set as Album Thumbnail, then the Album Thumbnail alone is not updated until after digikam is restarted.
I can confirm the pending problem from comment #12 Gilles Caulier
This problem still valid using last digiKam 5.0.0 ? Gilles Caulier
digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier
Hi Varun, digiKam 8.0.0 is out. Problem #2 listed in comment #12 still reproducible ? Best regards Gilles Caulier