Version: 2.0.0 (using KDE 4.6.2) OS: Linux I've observed this several times now, so I think it's a bug. I open the image in the image editor and do some other work. After a few minutes (maybe 5), I want to use the "colour/auto correction" (don't know the exact English name, since I use the German version, there it is "Farbe/Automatische Korrektur"), but it won't work. The progress bar is shown, but sits at 0%. I can cancel the job, but it won't change if I start it again. Other editing operations seem possible, as fas as I can see. Reproducible: Didn't try Steps to Reproduce: Open an image in the image editor wait for a few minutes choose "colour" from the menu choose the first item, something like "automatic correction" Actual Results: the progress bar in the lower left corner sits at 0%, nothing happens. Expected Results: The correction should proceed, so the progress bar also should show the progress of the operation. I only tried this with jpg images. I have no idea if this happens also with other image types.
Dysfunction is reproducible with another editor tool ? Note : I cannot reproduce it... Gilles Caulier
What other editor tool do you mean? It happens only in digikam's editor, and only with the colour auto-correction. Even after approximately 1 minute I can not use that function. all other editing functions work fine. BTW: the cursor turns into an hour glass or whatever while it does the job. After it got stuck once, the cursor doesn't return to its normal shape again, it remains the hour glass, whatever I do in digikam.
All editor functions are "tools", using same framework. Ex, White Balance, B&W converter, etc... Do you mean that tool is busy and compute ? What's the CPU idle ? Gilles Caulier
No, only Digikam is busy, or shows it is busy. But it doesn't really slow down anything. I can close the editor, open it again, and do the colour correction. Only the cursour shows the hour glass or the like, and not the arrow pointer. But only when it's over anything from digikam. Other tools, as said, work fine, it's only the colour/auto correction.
I can confirm the bug, I managed to reproduce once. A waiting time is needed seemingly so that all threads in the thread pool have exited (should be 30s). This indicates that under rarely occurring conditions, events may be delivered in unexpected order or whatever. Couldnt reliably reproduce since then.
I have this issue still in 2.1.0, and it happensvery regular, or better: there's no exception. I wonder what else it could be if you can't really reproduce it. It happens only to the color-correction tool, everything else works, and if I open another image from the thumbnail list, it works again fine. I've created a video about it, that can be downloaded here (5 MB): http://www.drmartinus.de/images/test-0000.mpeg
I could reproduce it once, but not always. So I believe there is a problem ;-) Would be easier to fix though if I could reproduce more regularly. Will try again, this may depend on random conditions.
Martin, This file still valid using digiKam 2.x serie ? Gilles Caulier
I haven't observed it any more with the latest releases, but I haven't checked it now.
Ok, I close this file as workforme. Re-open if necessary Gilles Caulier