digiKam version 4.10.0 Composant graphique Marble: 0.19.95 (0.20 Beta 3) Dématriçage parallélisé: Inconnu Exiv2 peut écrire dans un fichier JP2: Oui Exiv2 peut écrire dans un fichier JPEG: Oui Exiv2 peut écrire dans un fichier PGF: Oui Exiv2 peut écrire dans un fichier PNG: Oui Exiv2 peut écrire dans un fichier TIFF: Oui Exiv2 prend en charge les métadonnées XMP: Oui LibCImg: 130 LibEigen: 3.2.4 LibExiv2: 0.24 LibJPEG: 62 LibJasper: 1.900.1 LibKDE: 4.14.9 LibKExiv2: 2.4.0 LibKGeoMap: 3.1.0 LibKdcraw: 2.4.2 LibLCMS: 2060 LibLensFun: 0.2.8-0 LibPGF: 6.13.45 LibPNG: 1.6.10 LibQt: 4.8.6 LibRaw: 0.16.0 LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Prise en charge de LibLqr: oui Prise en charge du codec RawSpeed: Inconnu Prise en charge du pack Demosaic GPL2: Inconnu Prise en charge du pack Demosaic GPL3: Inconnu cœurs de processeur: 4 LibGphoto2: 2.5.7 LibKface: 3.5.0 LibKipi: 2.2.0 LibOpenCV: 2.4.9 Modules externes KIPI: 4.10.0 Moteur de base de données: QSQLITE Prise en charge de Baloo: Oui Prise en charge de SQLite2: non Prise en charge des KDEPIMlibs: Oui -- et aussi sur Facebook : _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I'm not sure if it with 4.11.0, but i remember that Maik Qualmaan has fixed something related with DB lock while processing images. This include BQM, MAintenance, and AdvanceRename tools. Gilles Caulier Le 26 juin 2015 20:41, Marie-Noëlle Augendre <[hidden email]> a écrit :
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Thanks for your answer, Gilles. I hope it is in 4.11.0, because otherwise the fix doesn't seem to work.2015-06-26 22:35 GMT+02:00 Gilles Caulier <[hidden email]>:
-- et aussi sur Facebook : _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In all cases, please follow instructions here about "For hangs out or dysfunctions" : in the console the trace will indicate the dysfunction. I'm sure that it's a DB file lock. Also, please explain well all stage done in GUI to reproduce the problem. Perhaps the problem is already reported in Bugzila. A lots of entries have been close as Wait for Info due to lack of feedback. I currently ping reporter again to make bugs alive, at least to see if problem are reproducible. To resume about 4.11.0 about bug triage : 90 files closed as fixed 110 files closed duplicates 70 files closed as wait for info 50 files as not reproducible. Gilles 2015-06-27 10:15 GMT+02:00 Marie-Noëlle Augendre <[hidden email]>:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
2015-06-27 10:31 GMT+02:00 Gilles Caulier <[hidden email]>:
First time I read this: "To turn on debug mode, use kdebugdialog tool to switch on right digiKam debug spaces before to run it, else nothing will be printed to the console." and I don"t find this very clear. It seems to have been automatically translated from some foreign language, but the result doesn't make much sense (at least for me, as english is not my native language). I tried to launch kdebugdialog in a console, and see a big "Debug Settings" list with checkboxes. I guess I have to uncheck everything but the Digikam settings. Will try this next time I'll have the problem. Marie-Noëlle _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
2015-06-27 13:29 GMT+02:00 Marie-Noëlle Augendre <[hidden email]>:
Yes exactly... Gilles Caulier _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |