Summary: | Group images by time puts multiple images in a progress queue, which never complete | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Parsifal.Herzog <Parsifal.Herzog> |
Component: | ProgressManager-Batch | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 2.6.0 | ||
Target Milestone: | --- | ||
Platform: | Mageia RPMs | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/digikam/eeb0c74b385d3c220dce8fba7167644a67add6d7 | Version Fixed In: | 2.8.0 |
Sentry Crash Report: |
Description
Parsifal.Herzog
2012-06-09 20:05:47 UTC
With respect to bug 295263, in which also the queued tasks failed to progress, I have found that selecting an image group, changing a tag, and choosing "Apply to all versions" rather than "Apply" (where problem was fixed) results in the same non-progressing tasks behaviour. I don't know if bug 295263 should be re-opened, but thought it relevant her because the problem relates to image groups. Git commit eeb0c74b385d3c220dce8fba7167644a67add6d7 by Marcel Wiesweg. Committed on 17/07/2012 at 21:50. Pushed by mwiesweg into branch 'master'. Creating a task with 0 items would introduce a progress item which never finishes. Generic fix and for the special case of group by time. M +2 -1 NEWS M +5 -0 digikam/fileaction/fileactionimageinfolist.cpp M +4 -1 digikam/items/digikamimageview.cpp http://commits.kde.org/digikam/eeb0c74b385d3c220dce8fba7167644a67add6d7 |