[Digikam-devel] [Bug 249023] New: Running the batch queue twice on same target directory fails with "Failed to save item..."
Alain Knaff
kde at kde.lka.org.lu
Wed Aug 25 18:23:37 BST 2010
https://bugs.kde.org/show_bug.cgi?id=249023
Summary: Running the batch queue twice on same target directory
fails with "Failed to save item..."
Product: digikam
Version: 1.2.0
Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Batch Queue Manager
AssignedTo: digikam-devel at kde.org
ReportedBy: kde at kde.lka.org.lu
Version: 1.2.0 (using KDE 4.4.2)
OS: Linux
When running the batch queue manager twice with the same target directory (but
different source files), it fails the second time with "Failed to save
item...".
It doesn't say _why_ it failed to save the item though...
Reproducible: Always
Steps to Reproduce:
1. Open the batch queue manager
2. Chose a target directory,
3. In behavior, select "Overwrite automatically"
4. In "File renaming", select "Use original filenames"
5. Add a couple of tools to the queue (such as Brightness/Contrast/Gamma and
Color Auto-Correction: Auto Exposure)
6. In main window, select a couple of photos, and add them to the batch queue
using Ctrl-B
7. Run the batch queue using the "Run" icon in the batch queue manager
8. After everything is completed, optionally clear the queue
9. Add some more items to the queue
10. Run it again
Actual Results:
On the second run, the actual processing steps succeed, but the result can't be
saved. Instead "Failed to save item..." is displayed.
A second run works fine if I change the target directory in between the runs.
Fortunately changing it to a different directory, and then back to the same
works too.
Expected Results:
I should be able to run the queue as many times I like, without fiddling with
the target directory in between runs
OS: Linux (x86_64) release 2.6.32-23-generic
Compiler: cc
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Digikam-devel
mailing list