Bug 408017 - Thumbnails disappear after workflow initiated
Summary: Thumbnails disappear after workflow initiated
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: BatchQueueManager-Workflow (show other bugs)
Version: 6.0.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-28 08:52 UTC by Chris Prior
Modified: 2019-07-26 17:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.2.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Prior 2019-05-28 08:52:16 UTC
SUMMARY
I have a workflow to create a jpeg reduced size copy of the files I have loaded in Digikam in raw (cr2) format.
Once the workflow has run, the thumbnails disappear. I have checked the file systems and the cr2 files are still in the designated folder. Also, the pictures can be seen if I select 'table' view.
Other thumbnails are still visible for folders where the workflow has not been run.

STEPS TO REPRODUCE
1. Select all files in folder
2. Run workflow (convert to jpeg, resize and save in different folder)
3. Thumbnails no longer appear

OBSERVED RESULT
Thumbnails missing

EXPECTED RESULT
Thumbnails still visible

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Gentoo 4.19.37, gcc 8.3.0
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
Worked fine in previous version of digikam
Comment 1 Maik Qualmann 2019-05-28 08:59:31 UTC
This was a bug in digiKam-6.0.0, this is fixed from digiKam-6.1.0. The versioning hides the original image. As a workaround you can activate the display of original image in the setup under versioning. Better, you are using a recent version of digiKam.

Maik
Comment 2 Maik Qualmann 2019-05-28 09:30:32 UTC

*** This bug has been marked as a duplicate of bug 405137 ***
Comment 3 caulier.gilles 2019-07-14 12:42:50 UTC
Fixed with #405137 and not reproducible with 6.2.0
Comment 4 caulier.gilles 2019-07-26 17:21:59 UTC
Fixed with bug #405137