Bug 194777 - synchronize images with database does not update all images if there are a lot of images in one album
Summary: synchronize images with database does not update all images if there are a lo...
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Date (show other bugs)
Version: 0.10.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-31 19:17 UTC by Christian Häne
Modified: 2022-01-10 20:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.5.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Häne 2009-05-31 19:17:54 UTC
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Gentoo Packages

When i use the menu item Album/Synchronize images with database on an album with lots of images with a certain size it begins happening that not every image is updated if i move a part of the images to a different album and then use run the synchronization it works. The size it begins happening is about 800 images.
Comment 1 caulier.gilles 2009-06-12 15:34:07 UTC
Sound like a bug fixed with 1.0.0-beta1. Can you try again with this version ?

Gilles Caulier
Comment 2 Andi Clemens 2009-06-29 21:11:11 UTC
Do you view this album recursively, or do you have over 800 items in a single album?
This might be a difference, so please give us an update here. I will test this when I'm sure what to test :-)

Andi
Comment 3 Christian Häne 2009-07-01 21:13:00 UTC
I have 1550 images in a single album. As soon as i have the time i will look at the development version. And also test if this bug is solved.
Comment 4 caulier.gilles 2009-07-11 11:08:03 UTC
Christian,

What's news here? 

Gilles Caulier
Comment 5 Marcel Wiesweg 2009-07-31 23:20:16 UTC
SVN commit 1005361 by mwiesweg:

Restructure some parts, with regards to recent changes (ensure progress info message is sent for
list-only parsing as well) and possible loophole for bug 194777.

CCBUG: 194777

 M  +19 -15    batchsyncmetadata.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1005361
Comment 6 Sean Reifschneider 2009-11-09 04:46:27 UTC
I am also seeing a similar problem, though with many fewer images.  This seemed to work almost flawlessly in 1.0 beta4, but has gotten quite bad in beta5.

This is definitely sporadic, though it does happen probably 50% of the time or more.  I've seen it happen with less than 100 images total (among all albums).

Steps to reproduce:

Tag some images.
Click "Apply" after adjusting tags.
Exit digiKam.
Use "exiv2" to read metadata from images.

Alternate steps to reproduce:

Tag some images.
Click "Apply" or not after adjusting tags.
Select "Tools -> Write Metadata to all Images".
Edit digiKam.
Use "exiv2" to read metadata from images.

Expected results: Tags found in "exiv2" output match tags which I set in digiKam.

Actual results: In some cases my images show *NO* tags, in some cases they just don't match.

To correct: When I see no tags, I seem to have to go back into digikam, de-select a tag, click "apply", re-select the tag, then do "Write Metadata to all Images".  Then exit digiKam and usually the tags are correct.
Comment 7 caulier.gilles 2011-12-16 16:32:01 UTC
Christian,

This file still valid using digiKAm 2.x serie ?

Gilles Caulier
Comment 8 caulier.gilles 2013-11-27 13:15:45 UTC
Christian,

This file still valid using digiKam 3.5.0 ?

Gilles Caulier
Comment 9 caulier.gilles 2015-06-30 08:07:26 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 10 caulier.gilles 2016-07-14 12:55:14 UTC
Christian,

digiKam 5.0.0 is published.

This problem still reproducible with this release ?

Gilles Caulier
Comment 11 caulier.gilles 2016-11-21 16:15:01 UTC
We need feedback with last digiKam AppImage Linux Bundle:

https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 12 caulier.gilles 2016-11-26 10:34:14 UTC
This problem still reproducible using digiKam AppImage bundle 5.4.0 pre release
?

It available at this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 13 caulier.gilles 2017-04-16 20:14:39 UTC
digiKam 5.5.0 is released officially

https://download.kde.org/stable/digikam/

...and new 5.6.0 pre-release as bundle is available here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Please check if this problem still reproducible with these versions.

Thanks in advance

Gilles Caulier
Comment 14 caulier.gilles 2017-06-22 21:39:09 UTC
digiKam 5.6.0 is now release and available as bundle for Linux, MacOS and Windows.

Can you check if problem still exists with this version ?

Thanks in advance

Gilles Caulier
Comment 15 caulier.gilles 2017-11-30 09:30:48 UTC
Please update this entry from bugzilla with current 5.8.0 pre-release bundle to see if problem remain.

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier
Comment 16 caulier.gilles 2018-12-31 11:40:50 UTC
Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just released ?

https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/

Gilles Caulier
Comment 17 caulier.gilles 2020-08-02 21:44:53 UTC
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
Comment 18 caulier.gilles 2022-01-10 20:58:51 UTC
No feedback. Closed