Sometimes (about 60% of time), after saving an image in edit mode (in non-destructive editing mode) and thus returning to preview mode, next image is not always loaded in the preview window. Reproducible: Sometimes Steps to Reproduce: 1. Open image in preview mode 2. Edit, do changes and save (non-destructive editing) 3. Close editor (saving image) Actual Results: Sometimes old image is still in preview mode, even though it is now an "original", since a new version has been created via edit. When pressing "next" shortcut, preview for next of next image is loaded. When after that pressing "back" shortcut, the correct image comes visible. it seems as if it has really jumped to the next image, but the new image is not replacing the image in the preview. Expected Results: Next image should be automatically loaded for preview. Happens sometimes.
Created attachment 83183 [details] Screenshot of bug situation This is what it looks like when the bug happens. It's like the image does not exist any more - next/prev buttons greyed out and all file properties for example empty. Context menu does not come up either.
Jason, I never seen this dysfunction before. Can you reproduce the problem using last digiKam 4.2.0 ? Gilles Caulier
Gilles, Will add a screenshot of the same thing happening on digiKam 4.0 - didn't try 4.2 yet as it doesn't install cleanly on my Ubuntu 14.04, some dependency requires updating and then apt-get wants to remove another app. If you think the problem could be resolved, I could try work around that. If it makes any difference all my images are on an NFS network drive. digikam 4:4.0.0-0ubuntu1~ubuntu14.04~ppa2
Created attachment 88681 [details] Screenshot of bug happening As you can see, thumbbar shows new image selected, preview shows pre-edit situation, but from thumbbar previous you can see clearly it has been changed. Next/prev buttons grayed out.
I think this was due to a badly setup NFS share. Once that was fixed I've not seen this after that. Maybe the transfer failed or failed to happen fast enough and digikam didn't move to the next image. Anyway, I'm closing this as it doesn't seem to be a problem in normal cases.