5.4.0 AppImage: Database locked when using BQM

[Oliver Schwabedissen]

Am 10.12.2016 um 11:43 schrieb Gilles Caulier:
> Maik has just commited this patch :
>
> Git commit f37ef2c195b61a43a40e9cbb7f119fdc8e9d38f4 by Maik Qualmann.
> Committed on 10/12/2016 at 10:16.
> Pushed by mqualmann into branch 'master'.
>
> fix locked database with BQM
>
> M  +24   -3    utilities/queuemanager/manager/actionthread.cpp
> M  +1    -0    utilities/queuemanager/manager/actionthread.h
> M  +5    -19   utilities/queuemanager/manager/task.cpp
>
> https://commits.kde.org/digikam/f37ef2c195b61a43a40e9cbb7f119fdc8e9d38f4
> <https://commits.kde.org/digikam/f37ef2c195b61a43a40e9cbb7f119fdc8e9d38f4>
>
> This must fix the problem. I will re-build the AppImage this week end.
> Still online.

I applied the patch to my Gentoo Digikam 5.3.0 version (meanwhile in
stable table tree) and it indeed fixed the problem!

Many thanks!

Oliver

> 2016-12-09 7:19 GMT+01:00 Oliver Schwabedissen
> <oliver at schwabedissen.name <mailto:oliver at schwabedissen.name>>:
>
>     Hello,
>
>     since version 5.3.0 I have a problem with the Batch Queue Manager:
>     whenever I try to sharpen more than a small number of images (eg.
>     4) the database locks and sharpening takes minutes or hangs
>     completely.
>
>     I tried this with V5.3.0 compiled on my System (Gentoo Linux 64
>     bit), 5.3.0 AppImage and now with 5.4.0 AppImage (both 64 bit).
>
>     Is this a problem with my database, my system or digikam?
>
>     Regards,
>
>     Oliver
>
>     -- 
>     GPG Public Key available at http://wwwkeys.de.pgp.net
>     Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507
>
>


-- 
GPG Public Key available at http://wwwkeys.de.pgp.net
Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20161210/8437473a/attachment.html>