[digiKam-users] --> Digikam 6.3 unstable and DEBUG

[Andrey Goreev]

I think appimage is Linux only. You need to download the version for Mac OS


On Fri, Sep 20, 2019 at 10:53 AM Alex Antão <alex at familiaturista.com.br>
wrote:

> No,
>
>     I use MacOSx. I migrated just the MacPhotos Library and want to use
> Digikam.
>     All on MacOS High Sierra, no Linux.
>
>     I'll try to start AppImage from terminal, although I've tried and
> didn't manage to, I'll try again.
> Thanks.
>
> ---- Ativado Sex, 20 set 2019 11:54:23 -0300 *Gilles Caulier
> <caulier.gilles at gmail.com <caulier.gilles at gmail.com>>* escreveu ----
>
> So if i understand correctly, you have used MAcOS and you migrate under
> Linux, as you use AppImage now.
>
> So, starting AppImage from the console must print a lots of debug
> statements. If not, there is a wrong settings somewhere in your system.
> Which Linux distribution do you use exactly ?
>
> Best
>
> Gilles Caulier
>
> Le ven. 20 sept. 2019 à 15:50, Alex Antão <alex at familiaturista.com.br> a
> écrit :
>
> Hi,
>
>     I'm running digikam om MacOSx High Sierra.
>     This 800Gb are a mix of Photos and videos. I have Photos in JPEG, PNG,
> HEIC and NEF formats.
>
>     This library was exported fom Mac Photos 3.0 and are all located in an
> external HD formated to HFS+.
>
>     Digikam ofter crashes on several parts, when I ask to recognize faces,
> to update Fingerprints (noticed that in a subset of the library this is
> more dificult to happen).
>     For example, the last time it crashes, I had selected a few photos,
> clicked on Tools tab, selected Tag Manager, it opened a window with all
> Tags, and when I closed it, it crashed.
>
>     I really want to migrate to Digikam, because my Photos App is not
> reliable anymore (discovered I have 720 photos missing on it, but it does
> not know, only when I try to export them), but I need Digikam to be stable
> enough to try to fullfill all my needs...
>
>     I'm runing it with AppImage, I don't have time to DEBUG it, but seeing
> the logs are suficiente to try to discover a possible problem and ask for
> help.
>
> Thanks....
>
>
>
>
> ---- Ativado Sex, 20 set 2019 10:32:55 -0300 *Gilles Caulier
> <caulier.gilles at gmail.com <caulier.gilles at gmail.com>>* escreveu ----
>
>
>
> Le jeu. 19 sept. 2019 à 21:41, Alex Antão <alex at familiaturista.com.br> a
> écrit :
>
>
> Hi,
>
>
>  I just downloaded the last version of Digikam.
>  My library is huge, about 800Gb with more than 100.000 photos, and I am
> still organizing it, from a export of Photos Library to a External HD.
>
>
> Hi,
>
> This is a very huge collection. I never tested in this kind of
> configuration. Yere my collection is about 200000 JPEG files but size is
> around 300 Gb on a SSD drive.
>
> Which kind of database do you use exactly ? where is stored this database ?
>
>
>
>
>  I don't know when exactly, but I'm felling digikam quite unstable. It
> crashes often. I am reorganizing the Library with some scripts I'm
> developing.
>  For example, I just opened it and it started scanning the changes I've
> done on the files, but when I click on my root Album, it crashes. But it
> does not if I left it untouched
>
>  I ordered it to generate Fingerprints and it crashes. But it does not if
> I select only one album to generate.
>
> I tried to open it from terminal to see if there are some error messages,
> but none was printed.
>
>
> It's abnormal. Your linux system hide Qt debug spaces with a default
> configuration. I already fixed this rule to under Centos. It just a text
> file to change on the system. Which Linux system do you use exactly ?
>
> Before to run digiKam set this env. variable :
>
> export QT_LOGGING_RULES="*.debug=true"
>
>
>
>
> Is there a way to debug and see what's going on?
>
>
> Yes, sure. With AppImage bundle, start digiKam with debug argument. It
> will run digiKam in GDB.
>
> If you don't use AppImage, just start digiKam in debugger as explained
> here :
>
> https://www.digikam.org/contribute/
>
> Best
>
> Gilles Caulier
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20190920/f90f7571/attachment.html>