[digiKam-users] Using Digikam after a long, long time and launching error

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

[digiKam-users] Using Digikam after a long, long time and launching error

tosca
Hi everybody, back after such a long time!

I haven't been using Digikam for a couple of years, and tried to use it again today.
First launch, everything seemed to be OK during the database migration, except for a warning about former batch procedures not being usable anymore as some tools had changed.
I was able to browse my albums and print a picture.

But subsequent launches don't work as I get these error messages:
 - Erreur - Analyse des collections, veuillez patienter... (but the gauge remains stuck at 0%)
 - Impossible d'effectuer la mise à jour du schéma de base données de la version 9 vers la version 10

And when launching again from a terminal, I get the following messages:
Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is created.
digikam.coredb: Core database: cannot process schema initialization
QThreadStorage: Thread 0x7f51c78e90e0 exited after QThreadStorage 12 destroyed

Please advise about how to handle this issue.
Thanks,
Marie-Noëlle


--
 
Découvrez mes photos sur mon site ou ma page Facebook




et tous mes livres-photos sur le site Blurb



Reply | Threaded
Open this post in threaded view
|

Re: Using Digikam after a long, long time and launching error

tosca
Hi everyone,

I just realised I had opted out messages delivery from the mailing-list, so I couldn't have received any answer if they were some.
Is there a way to browse the archived messages?

Thanks for helping,
Marie-Noëlle

Le lun. 27 janv. 2020 à 19:55, Marie-Noëlle Augendre <[hidden email]> a écrit :
Hi everybody, back after such a long time!

I haven't been using Digikam for a couple of years, and tried to use it again today.
First launch, everything seemed to be OK during the database migration, except for a warning about former batch procedures not being usable anymore as some tools had changed.
I was able to browse my albums and print a picture.

But subsequent launches don't work as I get these error messages:
 - Erreur - Analyse des collections, veuillez patienter... (but the gauge remains stuck at 0%)
 - Impossible d'effectuer la mise à jour du schéma de base données de la version 9 vers la version 10

And when launching again from a terminal, I get the following messages:
Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is created.
digikam.coredb: Core database: cannot process schema initialization
QThreadStorage: Thread 0x7f51c78e90e0 exited after QThreadStorage 12 destroyed

Please advise about how to handle this issue.
Thanks,
Marie-Noëlle


--
 
Découvrez mes photos sur mon site ou ma page Facebook




et tous mes livres-photos sur le site Blurb





--
 
Découvrez mes photos sur mon site ou ma page Facebook




et tous mes livres-photos sur le site Blurb



Reply | Threaded
Open this post in threaded view
|

Re: Using Digikam after a long, long time and launching error

Stuart T Rogers
Marie-Noelle

See https://mail.kde.org/mailman/listinfo/digikam-users to find the
archives.

Stuart

On 28/01/2020 10:23, Marie-Noëlle Augendre wrote:

> Hi everyone,
>
> I just realised I had opted out messages delivery from the mailing-list,
> so I couldn't have received any answer if they were some.
> Is there a way to browse the archived messages?
>
> Thanks for helping,
> Marie-Noëlle
>
> Le lun. 27 janv. 2020 à 19:55, Marie-Noëlle Augendre
> <[hidden email] <mailto:[hidden email]>> a écrit :
>
>     Hi everybody, back after such a long time!
>
>     I haven't been using Digikam for a couple of years, and tried to use
>     it again today.
>     First launch, everything seemed to be OK during the database
>     migration, except for a warning about former batch procedures not
>     being usable anymore as some tools had changed.
>     I was able to browse my albums and print a picture.
>
>     But subsequent launches don't work as I get these error messages:
>       - Erreur - Analyse des collections, veuillez patienter... (but the
>     gauge remains stuck at 0%)
>       - Impossible d'effectuer la mise à jour du schéma de base données
>     de la version 9 vers la version 10
>
>     And when launching again from a terminal, I get the following messages:
>     Attribute Qt::AA_ShareOpenGLContexts must be set before
>     QCoreApplication is created.
>     digikam.coredb: Core database: cannot process schema initialization
>     QThreadStorage: Thread 0x7f51c78e90e0 exited after QThreadStorage 12
>     destroyed
>
>     Please advise about how to handle this issue.
>     Thanks,
>     Marie-Noëlle
>
>
>     --
>     <http://marie-noelle-augendre.com>
>     Découvrez mes photos sur mon site <http://marie-noelle-augendre.com>
>     ou ma page Facebook
>     <https://www.facebook.com/PhotographeEnCevennes?ref=bookmarks>
>
>     <http://www.blurb.fr/user/mnaugendre><http://marie-noelle-augendre.com>
>     <http://www.blurb.fr/user/mnaugendre>
>
>     et tous mes livres-photos sur le site Blurb
>     <http://www.blurb.fr/user/mnaugendre>
>     <http://www.blurb.fr/user/mnaugendre>
>
>
>
>
>
> --
> <http://marie-noelle-augendre.com>
> Découvrez mes photos sur mon site <http://marie-noelle-augendre.com> ou
> ma page Facebook
> <https://www.facebook.com/PhotographeEnCevennes?ref=bookmarks>
>
> <http://www.blurb.fr/user/mnaugendre><http://marie-noelle-augendre.com>
> <http://www.blurb.fr/user/mnaugendre>
>
> et tous mes livres-photos sur le site Blurb
> <http://www.blurb.fr/user/mnaugendre>
> <http://www.blurb.fr/user/mnaugendre>
>
>
>

--
Website: https://www.stella-maris.org.uk
or:      https//www.broadstairs.org
Reply | Threaded
Open this post in threaded view
|

Re: Using Digikam after a long, long time and launching error

tosca
Hi Stuart,

Thank you very much for the link. I seem to have forgotten everything about using the list! :-)

Anyway, my initial question doesn't seem to have trigged any answer at the moment.
Anybody to help about this database migration issue?

Thanks in advance,
Marie-Noëlle

Le mar. 28 janv. 2020 à 11:27, Stuart T Rogers <[hidden email]> a écrit :
Marie-Noelle

See https://mail.kde.org/mailman/listinfo/digikam-users to find the
archives.

Stuart


> Le lun. 27 janv. 2020 à 19:55, Marie-Noëlle Augendre
> <[hidden email] <mailto:[hidden email]>> a écrit :
>
>     Hi everybody, back after such a long time!
>
>     I haven't been using Digikam for a couple of years, and tried to use
>     it again today.
>     First launch, everything seemed to be OK during the database
>     migration, except for a warning about former batch procedures not
>     being usable anymore as some tools had changed.
>     I was able to browse my albums and print a picture.
>
>     But subsequent launches don't work as I get these error messages:
>       - Erreur - Analyse des collections, veuillez patienter... (but the
>     gauge remains stuck at 0%)
>       - Impossible d'effectuer la mise à jour du schéma de base données
>     de la version 9 vers la version 10
>
>     And when launching again from a terminal, I get the following messages:
>     Attribute Qt::AA_ShareOpenGLContexts must be set before
>     QCoreApplication is created.
>     digikam.coredb: Core database: cannot process schema initialization
>     QThreadStorage: Thread 0x7f51c78e90e0 exited after QThreadStorage 12
>     destroyed
>
>     Please advise about how to handle this issue.
>     Thanks,
>     Marie-Noëlle
>
>

--
 
Découvrez mes photos sur mon site ou ma page Facebook




et tous mes livres-photos sur le site Blurb



Reply | Threaded
Open this post in threaded view
|

Re: Using Digikam after a long, long time and launching error

AndriusWild
Hi Marie-Noëlle

Please specify your version of digikam and OS.
It looks like you would rather file a bug report on bugs.kde.org then posting it as a question here but if I were you I would try to reproduce the issue with the latest weekly snapshot first. You can download it here:

https://files.kde.org/digikam/

Thanks,
Andrey

Sent from my Samsung Galaxy smartphone.


-------- Original message --------
From: Marie-Noëlle Augendre <[hidden email]>
Date: 2020-01-28 3:34 a.m. (GMT-07:00)
To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>
Subject: Re: [digiKam-users] Using Digikam after a long, long time and launching error

Hi Stuart,

Thank you very much for the link. I seem to have forgotten everything about using the list! :-)

Anyway, my initial question doesn't seem to have trigged any answer at the moment.
Anybody to help about this database migration issue?

Thanks in advance,
Marie-Noëlle

Le mar. 28 janv. 2020 à 11:27, Stuart T Rogers <[hidden email]> a écrit :
Marie-Noelle

See https://mail.kde.org/mailman/listinfo/digikam-users to find the
archives.

Stuart


> Le lun. 27 janv. 2020 à 19:55, Marie-Noëlle Augendre
> <[hidden email] <mailto:[hidden email]>> a écrit :
>
>     Hi everybody, back after such a long time!
>
>     I haven't been using Digikam for a couple of years, and tried to use
>     it again today.
>     First launch, everything seemed to be OK during the database
>     migration, except for a warning about former batch procedures not
>     being usable anymore as some tools had changed.
>     I was able to browse my albums and print a picture.
>
>     But subsequent launches don't work as I get these error messages:
>       - Erreur - Analyse des collections, veuillez patienter... (but the
>     gauge remains stuck at 0%)
>       - Impossible d'effectuer la mise à jour du schéma de base données
>     de la version 9 vers la version 10
>
>     And when launching again from a terminal, I get the following messages:
>     Attribute Qt::AA_ShareOpenGLContexts must be set before
>     QCoreApplication is created.
>     digikam.coredb: Core database: cannot process schema initialization
>     QThreadStorage: Thread 0x7f51c78e90e0 exited after QThreadStorage 12
>     destroyed
>
>     Please advise about how to handle this issue.
>     Thanks,
>     Marie-Noëlle
>
>

--
Reply | Threaded
Open this post in threaded view
|

Re: Using Digikam after a long, long time and launching error

Gilles Caulier-4


Le mar. 28 janv. 2020 à 07:18, Andrey Goreev <[hidden email]> a écrit :

Hi Marie-Noëlle

We need also the full debug trace printed on the console when your reproduce the problem. In fact, the use context is important.

Other question : which kind of database : sqlite, mysql, mariadb ? local, remote ?

Best

Gilles Caulier

Reply | Threaded
Open this post in threaded view
|

Re: Using Digikam after a long, long time and launching error

tosca
Hi Andrey and Gilles,

I'm running Linux Fedora, with Digikam 6.4.0
Database is local, and I didn't change the (old) defaut, so I guess it is still sqlite.
Following is the debug trace I got. Some things might be missing, but I don't what I need to do to get more.
Please let me know what to do next.
Marie-Noëlle

gdb digikam
GNU gdb (GDB) Fedora 8.3.50.20190824-26.fc31
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...
Reading symbols from /usr/lib/debug/usr/bin/digikam-6.4.0-2.fc31.x86_64.debug...
(gdb) catch throw
Catchpoint 1 (throw)
(gdb) run
Starting program: /usr/bin/digikam
Missing separate debuginfo for /lib64/libdigikamgui.so.6.4.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/0c/9369f14fd7cc7bc4059dc9f15331f7934d4e63.debug
Missing separate debuginfo for /lib64/libdigikamdatabase.so.6.4.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/6c/da38bc6f16c63c61c92125852476bd6e85cdea.debug
Missing separate debuginfo for /lib64/libdigikamcore.so.6.4.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/b2/d98db08928d4924096be73c9620bb5d2b82fb6.debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Missing separate debuginfo for /lib64/libmarblewidget-qt5.so.28
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/61/9ef2c86983a7a377f114a428e5a5de44ffbac4.debug
Missing separate debuginfo for /lib64/libsystemd.so.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/f7/31698af909f54c266d6ac774e25bcdff956192.debug
Missing separate debuginfo for /lib64/libudev.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/f8/0ae8613f31e66aac8aa639a13656b11887f6bd.debug
Missing separate debuginfo for /lib64/libuuid.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/97/f6854e8679ff15b4e5aa62eb96f6231f3a99db.debug
Missing separate debuginfo for /lib64/libastro.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/e2/dbf679d537fb845160795a3a0298dde41a0acf.debug
Missing separate debuginfo for /lib64/libnssutil3.so
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/59/030261c7fd02236d2baf6dbf186690f84a51cd.debug
[New Thread 0x7fffdbcdb700 (LWP 8243)]
Missing separate debuginfo for /lib64/libmount.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/7b/c4ea8502d2519255cb462361f780884a8cc18f.debug
Missing separate debuginfo for /lib64/libblkid.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/34/66b31186bed9f8475181e247478670630e50fc.debug
[New Thread 0x7fffda334700 (LWP 8244)]
[New Thread 0x7fffd9b33700 (LWP 8245)]
Missing separate debuginfo for /lib64/libGLX_mesa.so.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/d5/4f7d1425f6c709a36d0bbdc37e07af8da576ac.debug
Missing separate debuginfo for /lib64/libglapi.so.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/49/9e4db2bbe9cfa8c49e0edb96567e648caacb08.debug
Missing separate debuginfo for /usr/lib64/dri/nouveau_dri.so
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/da/0bd211cdf62f45c6d62e27b5dabf61676267c4.debug
[New Thread 0x7fffd8f4b700 (LWP 8251)]
Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is created.
[New Thread 0x7fffc5cef700 (LWP 8252)]
[New Thread 0x7fffc54ee700 (LWP 8253)]
[New Thread 0x7fffc4ced700 (LWP 8254)]
Missing separate debuginfo for /lib64/libsqlite3.so.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/55/5e7d9ec54bed4a64b6a6942ee03457a99a8148.debug
Missing separate debuginfo for /lib64/libnss_systemd.so.2
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/7a/00e500f894c76ac907481ac4c2ab8c946ccd1a.debug
[Thread 0x7fffc4ced700 (LWP 8254) exited]
digikam.coredb: Core database: cannot process schema initialization
[Thread 0x7fffdbcdb700 (LWP 8243) exited]
[Thread 0x7fffd8f4b700 (LWP 8251) exited]
[Thread 0x7fffc54ee700 (LWP 8253) exited]
QThreadStorage: Thread 0x7ffff7f850e0 exited after QThreadStorage 12 destroyed
[Thread 0x7fffc5cef700 (LWP 8252) exited]
[Thread 0x7fffd9b33700 (LWP 8245) exited]
[Thread 0x7fffe2a3a940 (LWP 8238) exited]
[Inferior 1 (process 8238) exited normally]
Missing separate debuginfos, use: dnf debuginfo-install ImageMagick-c++-6.9.10.86-1.fc31.x86_64 ImageMagick-libs-6.9.10.86-1.fc31.x86_64 OpenEXR-libs-2.3.0-4.fc31.x86_64 alsa-lib-1.2.1.2-4.fc31.x86_64 at-spi2-atk-2.34.1-1.fc31.x86_64 at-spi2-core-2.34.0-1.fc31.x86_64 atk-2.34.1-1.fc31.x86_64 bzip2-libs-1.0.8-1.fc31.x86_64 cairo-1.16.0-6.fc31.x86_64 cairo-gobject-1.16.0-6.fc31.x86_64 dbus-libs-1.12.16-3.fc31.x86_64 dbusmenu-qt5-0.9.3-0.21.20160218.fc31.x86_64 elfutils-libelf-0.178-7.fc31.x86_64 exiv2-libs-0.27.2-1.fc31.x86_64 expat-2.2.8-1.fc31.x86_64 fftw-libs-double-3.3.8-6.fc31.x86_64 flac-libs-1.3.3-1.fc31.x86_64 fontconfig-2.13.92-3.fc31.x86_64 freetype-2.10.0-3.fc31.x86_64 graphite2-1.3.13-1.fc31.x86_64 gsm-1.0.18-5.fc31.x86_64 gtk3-3.24.13-1.fc31.x86_64 harfbuzz-2.6.1-2.fc31.x86_64 ilmbase-2.3.0-3.fc31.x86_64 jasper-libs-2.0.14-9.fc31.x86_64 jbigkit-libs-2.1-17.fc31.x86_64 kf5-akonadi-contacts-19.04.3-2.fc31.x86_64 kf5-akonadi-server-19.04.3-4.fc31.x86_64 kf5-attica-5.66.0-2.fc31.x86_64 kf5-karchive-5.66.0-1.fc31.x86_64 kf5-kcodecs-5.66.0-1.fc31.x86_64 kf5-kconfig-core-5.66.0-1.fc31.x86_64 kf5-kconfig-gui-5.66.0-1.fc31.x86_64 kf5-kconfigwidgets-5.66.0-1.fc31.x86_64 kf5-kcoreaddons-5.66.0-1.fc31.x86_64 kf5-kcrash-5.66.0-1.fc31.x86_64 kf5-kfilemetadata-5.66.0-2.fc31.x86_64 kf5-kglobalaccel-libs-5.66.0-1.fc31.x86_64 kf5-kguiaddons-5.66.0-1.fc31.x86_64 kf5-ki18n-5.66.0-1.fc31.x86_64 kf5-kiconthemes-5.66.0-1.fc31.x86_64 kf5-kimageformats-5.66.0-1.fc31.x86_64 kf5-kio-core-libs-5.66.0-1.fc31.x86_64 kf5-kio-widgets-libs-5.66.0-1.fc31.x86_64 kf5-kitemviews-5.66.0-1.fc31.x86_64 kf5-kmime-19.04.3-1.fc31.x86_64 kf5-knotifyconfig-5.66.0-1.fc31.x86_64 kf5-kservice-5.66.0-1.fc31.x86_64 kf5-ktextwidgets-5.66.0-1.fc31.x86_64 kf5-kwidgetsaddons-5.66.0-1.fc31.x86_64 kf5-kwindowsystem-5.66.0-1.fc31.x86_64 kf5-kxmlgui-5.66.0-1.fc31.x86_64 kf5-solid-5.66.0-1.fc31.x86_64 lcms2-2.9-6.fc31.x86_64 lensfun-0.3.2-22.fc31.x86_64 libICE-1.0.10-2.fc31.x86_64 libSM-1.2.3-4.fc31.x86_64 libX11-1.6.9-2.fc31.x86_64 libX11-xcb-1.6.9-2.fc31.x86_64 libXau-1.0.9-2.fc31.x86_64 libXcursor-1.1.15-6.fc31.x86_64 libXext-1.3.4-2.fc31.x86_64 libXfixes-5.0.3-10.fc31.x86_64 libXinerama-1.1.4-4.fc31.x86_64 libXrandr-1.5.2-2.fc31.x86_64 libXt-1.1.5-12.20190424gitba4ec9376.fc31.x86_64 libattr-2.4.48-7.fc31.x86_64 libcap-2.26-6.fc31.x86_64 libdatrie-0.2.9-10.fc31.x86_64 libepoxy-1.5.3-4.fc31.x86_64 libevent-2.1.8-7.fc31.x86_64 libexif-0.6.21-20.fc31.x86_64 libffi-3.1-23.fc31.x86_64 libgcc-9.2.1-1.fc31.x86_64 libglvnd-1.1.1-5.fc31.x86_64 libglvnd-glx-1.1.1-5.fc31.x86_64 libgomp-9.2.1-1.fc31.x86_64 libgphoto2-2.5.23-1.fc31.x86_64 libicu-63.2-3.fc31.x86_64 liblqr-1-0.4.2-13.fc31.x86_64 libmng-2.0.3-10.fc31.x86_64 libpng-1.6.37-2.fc31.x86_64 libraqm-0.7.0-4.fc31.x86_64 libselinux-2.9-5.fc31.x86_64 libstdc++-9.2.1-1.fc31.x86_64 libva-2.6.0-0.1.fc31.x86_64 libwayland-cursor-1.17.0-2.fc31.x86_64 libwebp-1.0.3-2.fc31.x86_64 libxcb-1.13.1-3.fc31.x86_64 libxkbcommon-0.9.1-3.fc31.x86_64 libxml2-2.9.10-2.fc31.x86_64 llvm-libs-9.0.0-1.fc31.x86_64 lz4-libs-1.9.1-1.fc31.x86_64 ncurses-libs-6.1-12.20190803.fc31.x86_64 openblas-serial-0.3.7-1.fc31.x86_64 opencv-core-3.4.8-1.fc31.x86_64 openssl-libs-1.1.1d-2.fc31.x86_64 pango-1.44.7-1.fc31.x86_64 pcre-8.43-2.fc31.1.x86_64 pcre2-10.34-4.fc31.x86_64 phonon-qt5-4.10.2-3.fc31.x86_64 pixman-0.38.4-1.fc31.x86_64 qt5-qtbase-5.13.2-1.fc31.x86_64 qt5-qtbase-gui-5.13.2-1.fc31.x86_64 qt5-qtspeech-5.13.2-1.fc31.x86_64 qt5-qtsvg-5.13.2-1.fc31.x86_64 qt5-qtwebchannel-5.13.2-1.fc31.x86_64 qt5-qtwebengine-5.13.2-1.fc31.x86_64 re2-20190801-3.fc31.x86_64 snappy-1.1.7-9.fc31.x86_64 xcb-util-keysyms-0.4.0-11.fc31.x86_64 xcb-util-renderutil-0.3.9-14.fc31.x86_64 xcb-util-wm-0.4.1-16.fc31.x86_64 xz-libs-5.2.4-6.fc31.x86_64
(gdb) bt
No stack.
(gdb)



Le mar. 28 janv. 2020 à 14:00, Gilles Caulier <[hidden email]> a écrit :


Le mar. 28 janv. 2020 à 07:18, Andrey Goreev <[hidden email]> a écrit :

Hi Marie-Noëlle

We need also the full debug trace printed on the console when your reproduce the problem. In fact, the use context is important.

Other question : which kind of database : sqlite, mysql, mariadb ? local, remote ?

Best

Gilles Caulier



--
 
Découvrez mes photos sur mon site ou ma page Facebook




et tous mes livres-photos sur le site Blurb



Reply | Threaded
Open this post in threaded view
|

Re: Using Digikam after a long, long time and launching error

Gilles Caulier-4
Thanks Marie Noel,

By debug trace on the console, i want mean the trace printed by digiKam while running, not the gdb backtrace (in your case, there is nothing to read, as the application do not crash).

Gilles

Le mar. 28 janv. 2020 à 14:55, Marie-Noëlle Augendre <[hidden email]> a écrit :
Hi Andrey and Gilles,

I'm running Linux Fedora, with Digikam 6.4.0
Database is local, and I didn't change the (old) defaut, so I guess it is still sqlite.
Following is the debug trace I got. Some things might be missing, but I don't what I need to do to get more.
Please let me know what to do next.
Marie-Noëlle

gdb digikam
GNU gdb (GDB) Fedora 8.3.50.20190824-26.fc31
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...
Reading symbols from /usr/lib/debug/usr/bin/digikam-6.4.0-2.fc31.x86_64.debug...
(gdb) catch throw
Catchpoint 1 (throw)
(gdb) run
Starting program: /usr/bin/digikam
Missing separate debuginfo for /lib64/libdigikamgui.so.6.4.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/0c/9369f14fd7cc7bc4059dc9f15331f7934d4e63.debug
Missing separate debuginfo for /lib64/libdigikamdatabase.so.6.4.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/6c/da38bc6f16c63c61c92125852476bd6e85cdea.debug
Missing separate debuginfo for /lib64/libdigikamcore.so.6.4.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/b2/d98db08928d4924096be73c9620bb5d2b82fb6.debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Missing separate debuginfo for /lib64/libmarblewidget-qt5.so.28
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/61/9ef2c86983a7a377f114a428e5a5de44ffbac4.debug
Missing separate debuginfo for /lib64/libsystemd.so.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/f7/31698af909f54c266d6ac774e25bcdff956192.debug
Missing separate debuginfo for /lib64/libudev.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/f8/0ae8613f31e66aac8aa639a13656b11887f6bd.debug
Missing separate debuginfo for /lib64/libuuid.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/97/f6854e8679ff15b4e5aa62eb96f6231f3a99db.debug
Missing separate debuginfo for /lib64/libastro.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/e2/dbf679d537fb845160795a3a0298dde41a0acf.debug
Missing separate debuginfo for /lib64/libnssutil3.so
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/59/030261c7fd02236d2baf6dbf186690f84a51cd.debug
[New Thread 0x7fffdbcdb700 (LWP 8243)]
Missing separate debuginfo for /lib64/libmount.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/7b/c4ea8502d2519255cb462361f780884a8cc18f.debug
Missing separate debuginfo for /lib64/libblkid.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/34/66b31186bed9f8475181e247478670630e50fc.debug
[New Thread 0x7fffda334700 (LWP 8244)]
[New Thread 0x7fffd9b33700 (LWP 8245)]
Missing separate debuginfo for /lib64/libGLX_mesa.so.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/d5/4f7d1425f6c709a36d0bbdc37e07af8da576ac.debug
Missing separate debuginfo for /lib64/libglapi.so.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/49/9e4db2bbe9cfa8c49e0edb96567e648caacb08.debug
Missing separate debuginfo for /usr/lib64/dri/nouveau_dri.so
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/da/0bd211cdf62f45c6d62e27b5dabf61676267c4.debug
[New Thread 0x7fffd8f4b700 (LWP 8251)]
Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is created.
[New Thread 0x7fffc5cef700 (LWP 8252)]
[New Thread 0x7fffc54ee700 (LWP 8253)]
[New Thread 0x7fffc4ced700 (LWP 8254)]
Missing separate debuginfo for /lib64/libsqlite3.so.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/55/5e7d9ec54bed4a64b6a6942ee03457a99a8148.debug
Missing separate debuginfo for /lib64/libnss_systemd.so.2
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/7a/00e500f894c76ac907481ac4c2ab8c946ccd1a.debug
[Thread 0x7fffc4ced700 (LWP 8254) exited]
digikam.coredb: Core database: cannot process schema initialization
[Thread 0x7fffdbcdb700 (LWP 8243) exited]
[Thread 0x7fffd8f4b700 (LWP 8251) exited]
[Thread 0x7fffc54ee700 (LWP 8253) exited]
QThreadStorage: Thread 0x7ffff7f850e0 exited after QThreadStorage 12 destroyed
[Thread 0x7fffc5cef700 (LWP 8252) exited]
[Thread 0x7fffd9b33700 (LWP 8245) exited]
[Thread 0x7fffe2a3a940 (LWP 8238) exited]
[Inferior 1 (process 8238) exited normally]
Missing separate debuginfos, use: dnf debuginfo-install ImageMagick-c++-6.9.10.86-1.fc31.x86_64 ImageMagick-libs-6.9.10.86-1.fc31.x86_64 OpenEXR-libs-2.3.0-4.fc31.x86_64 alsa-lib-1.2.1.2-4.fc31.x86_64 at-spi2-atk-2.34.1-1.fc31.x86_64 at-spi2-core-2.34.0-1.fc31.x86_64 atk-2.34.1-1.fc31.x86_64 bzip2-libs-1.0.8-1.fc31.x86_64 cairo-1.16.0-6.fc31.x86_64 cairo-gobject-1.16.0-6.fc31.x86_64 dbus-libs-1.12.16-3.fc31.x86_64 dbusmenu-qt5-0.9.3-0.21.20160218.fc31.x86_64 elfutils-libelf-0.178-7.fc31.x86_64 exiv2-libs-0.27.2-1.fc31.x86_64 expat-2.2.8-1.fc31.x86_64 fftw-libs-double-3.3.8-6.fc31.x86_64 flac-libs-1.3.3-1.fc31.x86_64 fontconfig-2.13.92-3.fc31.x86_64 freetype-2.10.0-3.fc31.x86_64 graphite2-1.3.13-1.fc31.x86_64 gsm-1.0.18-5.fc31.x86_64 gtk3-3.24.13-1.fc31.x86_64 harfbuzz-2.6.1-2.fc31.x86_64 ilmbase-2.3.0-3.fc31.x86_64 jasper-libs-2.0.14-9.fc31.x86_64 jbigkit-libs-2.1-17.fc31.x86_64 kf5-akonadi-contacts-19.04.3-2.fc31.x86_64 kf5-akonadi-server-19.04.3-4.fc31.x86_64 kf5-attica-5.66.0-2.fc31.x86_64 kf5-karchive-5.66.0-1.fc31.x86_64 kf5-kcodecs-5.66.0-1.fc31.x86_64 kf5-kconfig-core-5.66.0-1.fc31.x86_64 kf5-kconfig-gui-5.66.0-1.fc31.x86_64 kf5-kconfigwidgets-5.66.0-1.fc31.x86_64 kf5-kcoreaddons-5.66.0-1.fc31.x86_64 kf5-kcrash-5.66.0-1.fc31.x86_64 kf5-kfilemetadata-5.66.0-2.fc31.x86_64 kf5-kglobalaccel-libs-5.66.0-1.fc31.x86_64 kf5-kguiaddons-5.66.0-1.fc31.x86_64 kf5-ki18n-5.66.0-1.fc31.x86_64 kf5-kiconthemes-5.66.0-1.fc31.x86_64 kf5-kimageformats-5.66.0-1.fc31.x86_64 kf5-kio-core-libs-5.66.0-1.fc31.x86_64 kf5-kio-widgets-libs-5.66.0-1.fc31.x86_64 kf5-kitemviews-5.66.0-1.fc31.x86_64 kf5-kmime-19.04.3-1.fc31.x86_64 kf5-knotifyconfig-5.66.0-1.fc31.x86_64 kf5-kservice-5.66.0-1.fc31.x86_64 kf5-ktextwidgets-5.66.0-1.fc31.x86_64 kf5-kwidgetsaddons-5.66.0-1.fc31.x86_64 kf5-kwindowsystem-5.66.0-1.fc31.x86_64 kf5-kxmlgui-5.66.0-1.fc31.x86_64 kf5-solid-5.66.0-1.fc31.x86_64 lcms2-2.9-6.fc31.x86_64 lensfun-0.3.2-22.fc31.x86_64 libICE-1.0.10-2.fc31.x86_64 libSM-1.2.3-4.fc31.x86_64 libX11-1.6.9-2.fc31.x86_64 libX11-xcb-1.6.9-2.fc31.x86_64 libXau-1.0.9-2.fc31.x86_64 libXcursor-1.1.15-6.fc31.x86_64 libXext-1.3.4-2.fc31.x86_64 libXfixes-5.0.3-10.fc31.x86_64 libXinerama-1.1.4-4.fc31.x86_64 libXrandr-1.5.2-2.fc31.x86_64 libXt-1.1.5-12.20190424gitba4ec9376.fc31.x86_64 libattr-2.4.48-7.fc31.x86_64 libcap-2.26-6.fc31.x86_64 libdatrie-0.2.9-10.fc31.x86_64 libepoxy-1.5.3-4.fc31.x86_64 libevent-2.1.8-7.fc31.x86_64 libexif-0.6.21-20.fc31.x86_64 libffi-3.1-23.fc31.x86_64 libgcc-9.2.1-1.fc31.x86_64 libglvnd-1.1.1-5.fc31.x86_64 libglvnd-glx-1.1.1-5.fc31.x86_64 libgomp-9.2.1-1.fc31.x86_64 libgphoto2-2.5.23-1.fc31.x86_64 libicu-63.2-3.fc31.x86_64 liblqr-1-0.4.2-13.fc31.x86_64 libmng-2.0.3-10.fc31.x86_64 libpng-1.6.37-2.fc31.x86_64 libraqm-0.7.0-4.fc31.x86_64 libselinux-2.9-5.fc31.x86_64 libstdc++-9.2.1-1.fc31.x86_64 libva-2.6.0-0.1.fc31.x86_64 libwayland-cursor-1.17.0-2.fc31.x86_64 libwebp-1.0.3-2.fc31.x86_64 libxcb-1.13.1-3.fc31.x86_64 libxkbcommon-0.9.1-3.fc31.x86_64 libxml2-2.9.10-2.fc31.x86_64 llvm-libs-9.0.0-1.fc31.x86_64 lz4-libs-1.9.1-1.fc31.x86_64 ncurses-libs-6.1-12.20190803.fc31.x86_64 openblas-serial-0.3.7-1.fc31.x86_64 opencv-core-3.4.8-1.fc31.x86_64 openssl-libs-1.1.1d-2.fc31.x86_64 pango-1.44.7-1.fc31.x86_64 pcre-8.43-2.fc31.1.x86_64 pcre2-10.34-4.fc31.x86_64 phonon-qt5-4.10.2-3.fc31.x86_64 pixman-0.38.4-1.fc31.x86_64 qt5-qtbase-5.13.2-1.fc31.x86_64 qt5-qtbase-gui-5.13.2-1.fc31.x86_64 qt5-qtspeech-5.13.2-1.fc31.x86_64 qt5-qtsvg-5.13.2-1.fc31.x86_64 qt5-qtwebchannel-5.13.2-1.fc31.x86_64 qt5-qtwebengine-5.13.2-1.fc31.x86_64 re2-20190801-3.fc31.x86_64 snappy-1.1.7-9.fc31.x86_64 xcb-util-keysyms-0.4.0-11.fc31.x86_64 xcb-util-renderutil-0.3.9-14.fc31.x86_64 xcb-util-wm-0.4.1-16.fc31.x86_64 xz-libs-5.2.4-6.fc31.x86_64
(gdb) bt
No stack.
(gdb)



Le mar. 28 janv. 2020 à 14:00, Gilles Caulier <[hidden email]> a écrit :


Le mar. 28 janv. 2020 à 07:18, Andrey Goreev <[hidden email]> a écrit :

Hi Marie-Noëlle

We need also the full debug trace printed on the console when your reproduce the problem. In fact, the use context is important.

Other question : which kind of database : sqlite, mysql, mariadb ? local, remote ?

Best

Gilles Caulier



--
 
Découvrez mes photos sur mon site ou ma page Facebook




et tous mes livres-photos sur le site Blurb



Reply | Threaded
Open this post in threaded view
|

Re: Using Digikam after a long, long time and launching error

tosca
Oups, sorry!

That should be this:
[marie-noelle@new-host-2 ~]$ export QT_LOGGING_RULES="digikam*=true"
[marie-noelle@new-host-2 ~]$ digikam
Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is created.
digikam.widgets: Use installed icons
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
   Type:                     "QSQLITE"
   DB Core Name:             "/home/marie-noelle/DK-fixe/digikam4.db"
   DB Thumbs Name:           "/home/marie-noelle/DK-fixe/thumbnails-digikam.db"
   DB Face Name:             "/home/marie-noelle/DK-fixe/recognition.db"
   DB Similarity Name:       "/home/marie-noelle/DK-fixe/similarity.db"
   Connect Options:          ""
   Host Name:                ""
   Host port:                -1
   Internal Server:          false
   Internal Server Path:     ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username:                 ""
   Password:                 ""

digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  9
digikam.coredb: Core database: makeUpdates  9  to  10
digikam.dbengine: Failure executing query:
 ""
Error messages: "Unable to execute statement" "duplicate column name: manualOrder" "1" 2
Bound values:  ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV9ToV10" ] Statement [ "ALTER TABLE Images ADD manualOrder INTEGER;" ]
digikam.coredb: Core database: schema update to V 10 failed!
digikam.coredb: Core database: cannot process schema initialization
digikam.general: Allowing a cache size of 195 MB
QThreadStorage: Thread 0x7f1796f640e0 exited after QThreadStorage 12 destroyed
[marie-noelle@new-host-2 ~]$

Marie-Noëlle


Le mar. 28 janv. 2020 à 15:08, Gilles Caulier <[hidden email]> a écrit :
Thanks Marie Noel,

By debug trace on the console, i want mean the trace printed by digiKam while running, not the gdb backtrace (in your case, there is nothing to read, as the application do not crash).

Gilles

--
 
Découvrez mes photos sur mon site ou ma page Facebook




et tous mes livres-photos sur le site Blurb



Reply | Threaded
Open this post in threaded view
|

Re: Using Digikam after a long, long time and launching error

Maik Qualmann
Hi Marie-Noëlle

The reason is that you tried beta versions where we added a table column. Now
with the official version the application fails. Copy the attached
dbconfig.xml file to "/usr/share/digikam/database/". Replace the existing one,
I hope Fedore also installs digiKam in this directory. Now the update should
go through without any problems.

The attached file is a ZIP file, so you have to unzip it first.

Maik

Am Dienstag, 28. Januar 2020, 15:19:20 CET schrieb Marie-Noëlle Augendre:

> Oups, sorry!
>
> That should be this:
> [marie-noelle@new-host-2 ~]$ export QT_LOGGING_RULES="digikam*=true"
> [marie-noelle@new-host-2 ~]$ digikam
> Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is
> created.
> digikam.widgets: Use installed icons
> digikam.general: AlbumWatch is disabled
> digikam.general: Database Parameters:
>    Type:                     "QSQLITE"
>    DB Core Name:             "/home/marie-noelle/DK-fixe/digikam4.db"
>    DB Thumbs Name:
> "/home/marie-noelle/DK-fixe/thumbnails-digikam.db"
>    DB Face Name:             "/home/marie-noelle/DK-fixe/recognition.db"
>    DB Similarity Name:       "/home/marie-noelle/DK-fixe/similarity.db"
>    Connect Options:          ""
>    Host Name:                ""
>    Host port:                -1
>    Internal Server:          false
>    Internal Server Path:     ""
>    Internal Server Serv Cmd: ""
>    Internal Server Init Cmd: ""
>    Username:                 ""
>    Password:                 ""
>
> digikam.dbengine: Loading SQL code from config file
> "/usr/share/digikam/database/dbconfig.xml"
> digikam.dbengine: Checking XML version ID => expected:  3  found:  3
> digikam.coredb: Core database: running schema update
> digikam.coredb: Core database: have a structure version  9
> digikam.coredb: Core database: makeUpdates  9  to  10
> digikam.dbengine: Failure executing query:
>  ""
> Error messages: "Unable to execute statement" "duplicate column name:
> manualOrder" "1" 2
> Bound values:  ()
> digikam.dbengine: Error while executing DBAction [
> "UpdateSchemaFromV9ToV10" ] Statement [ "ALTER TABLE Images ADD manualOrder
> INTEGER;" ]
> digikam.coredb: Core database: schema update to V 10 failed!
> digikam.coredb: Core database: cannot process schema initialization
> digikam.general: Allowing a cache size of 195 MB
> QThreadStorage: Thread 0x7f1796f640e0 exited after QThreadStorage 12
> destroyed
> [marie-noelle@new-host-2 ~]$
>
> Marie-Noëlle
>
>
> Le mar. 28 janv. 2020 à 15:08, Gilles Caulier <[hidden email]> a
>
> écrit :
> > Thanks Marie Noel,
> >
> > By debug trace on the console, i want mean the trace printed by digiKam
> > while running, not the gdb backtrace (in your case, there is nothing to
> > read, as the application do not crash).
> >
> > Gilles
> >
> > --
>
>   <http://marie-noelle-augendre.com>
> Découvrez mes photos sur mon site <http://marie-noelle-augendre.com> ou ma
> page Facebook <https://www.facebook.com/PhotographeEnCevennes?ref=bookmarks>
>
> <http://www.blurb.fr/user/mnaugendre> <http://marie-noelle-augendre.com>
> <http://www.blurb.fr/user/mnaugendre>
>
> et tous mes livres-photos sur le site Blurb
> <http://www.blurb.fr/user/mnaugendre>
> <http://www.blurb.fr/user/mnaugendre>


dbconfig.zip (21K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Using Digikam after a long, long time and launching error

tosca
Hi Maik,

Thank you so much for the file and the instructions. That worked fine, and I now have access to my albums.

Marie-Noëlle

Le mar. 28 janv. 2020 à 20:35, Maik Qualmann <[hidden email]> a écrit :
Hi Marie-Noëlle

The reason is that you tried beta versions where we added a table column. Now
with the official version the application fails. Copy the attached
dbconfig.xml file to "/usr/share/digikam/database/". Replace the existing one,
I hope Fedore also installs digiKam in this directory. Now the update should
go through without any problems.

The attached file is a ZIP file, so you have to unzip it first.

Maik

--
 
Découvrez mes photos sur mon site ou ma page Facebook




et tous mes livres-photos sur le site Blurb