Bug 406809 - digikam-6.2.0-git-20190421T121202-qtwebengine-x86-64.appimage crashes on startup.
Summary: digikam-6.2.0-git-20190421T121202-qtwebengine-x86-64.appimage crashes on star...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Bundle-AppImage (show other bugs)
Version: 6.2.0
Platform: Appimage Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-23 13:02 UTC by MarcP
Modified: 2020-08-10 10:18 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.0.0


Attachments
Debug log (82.06 KB, text/plain)
2019-08-30 13:02 UTC, Sean O'Neill
Details
Windows crash report - (16.98 KB, text/plain)
2019-08-30 13:25 UTC, Sean O'Neill
Details
attachment-10062-0.html (3.32 KB, text/html)
2019-08-30 18:22 UTC, Sean O'Neill
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MarcP 2019-04-23 13:02:36 UTC
SUMMARY

I just noticed that the last appimage available, digikam-6.2.0-git-20190421T121202-qtwebengine-x86-64, crashes on startup. Previous versions work fine.

This is what I see when launched from a console:



[New Thread 0x7fff457fa700 (LWP 4894)]
[4457:4882:0423/143320.482389:ERROR:nss_util.cc(653)] Error initializing NSS with a persistent database (sql:/home/user/.pki/nssdb): libsoftokn3.so: cannot open shared object file: El fitxer o directori no existeix
[4457:4882:0423/143320.482603:ERROR:nss_util.cc(154)] Error initializing NSS without a persistent database: NSS error code: -5925
[4457:4882:0423/143320.482628:FATAL:nss_util.cc(156)] nss_error=-5925, os_error=0

Thread 31 "Chrome_IOThread" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fff68ff9700 (LWP 4882)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51	../sysdeps/unix/sysv/linux/raise.c: El fitxer o directori no existeix.
(gdb)  




SOFTWARE/OS VERSIONS

Ubuntu 18.04 with gnome
Comment 1 caulier.gilles 2019-04-23 14:34:37 UTC
This error come from openssh & co.

Sound like it do not found the libsoftokn3.so shared library on your system.

Q : when you said "Previous versions work fine"... Which one exactly ? Official 6.1.0 ? This is strange because i don't change anything about openssh since 6.1.0 is released...

Gilles Caulier
Comment 2 MarcP 2019-04-23 17:06:46 UTC
digikam-6.2.0-git-20190416T091455-qtwebkit-x86-64 works perfectly for me. The newest one (git-20190421T121202) crashes on launch.
Comment 3 Maik Qualmann 2019-04-23 19:31:35 UTC
You compare 2 different AppImages "qtwebkit" and "qwebengine". The AppImage built with "qwebengine" is more beta and currently more of a test, it needs good OpenGL support. Even if the problem is more due to a missing library.

Maik
Comment 4 MarcP 2019-04-23 23:57:15 UTC
Ah, ok. At the moment I checked the website for new versions, there wasn't any qtwebkit, only the qwebengine, so I thought the qtwebkit one was deprecated or something. Now I see that there are both again.
Comment 5 caulier.gilles 2019-04-24 07:47:29 UTC
For more details : the official appimage 6.1.0 use QtWebkit, as QtWebEngine is not enough stable. In fact AppImage use currently Qt 5.11.3, and we need at least to use last Qt 5.12.2 to plan to migrate under QtWebEngine.

So, as Maik said, QtWebEngine version is just experimental. Use QtWebkit instead.

Gilles Caulier
Comment 6 Sean O'Neill 2019-08-30 09:43:51 UTC
Cannot upgrade from Digikam 5.8 to version 6.2.0 64-bit. Get error message: "Failed to update the database schema from version 9 to version 10". Then program shuts down. Have tried to uninstall Digikam entirely several times, but same message displays each time and problem persist.
Comment 7 Maik Qualmann 2019-08-30 10:28:12 UTC
Download "DebugView" from Microsoft and start it. Start digiKam until the error and post the messages that are now included in DebugView.

Maik
Comment 8 Sean O'Neill 2019-08-30 13:02:50 UTC
Created attachment 122420 [details]
Debug log
Comment 9 Sean O'Neill 2019-08-30 13:25:25 UTC
Created attachment 122421 [details]
Windows crash report -
Comment 10 Maik Qualmann 2019-08-30 16:26:31 UTC
Somehow you started 2 digiKam instances at the same time, if I interpret it correctly in the log. The reason is that the table column "manualOrder" already exists. I suspect that you have tested beta version of digiKam 5.x.x and now the database is failing to update. It's best to move "C:\Users\Sean\Pictures\digikam4.db" to a safe location and digiKam will create a new database. Later you can use the migration tool in digiKam to copy the old digikam4.db into the new one.

Maik
Comment 11 Sean O'Neill 2019-08-30 18:22:59 UTC
Created attachment 122429 [details]
attachment-10062-0.html

Thank you. Maik.

That worked fine. I can open and use Digikam 6.2.0 now.

Regards
Sean



Sent from Mail for Windows 10

From: Maik Qualmann
Sent: 30 August 2019 17:26
To: aobr29998@blueyonder.co.uk
Subject: [digikam] [Bug 406809]digikam-6.2.0-git-20190421T121202-qtwebengine-x86-64.appimage crashes onstartup.

https://bugs.kde.org/show_bug.cgi?id=406809

--- Comment #10 from Maik Qualmann <metzpinguin@gmail.com> ---
Somehow you started 2 digiKam instances at the same time, if I interpret it
correctly in the log. The reason is that the table column "manualOrder" already
exists. I suspect that you have tested beta version of digiKam 5.x.x and now
the database is failing to update. It's best to move
"C:\Users\Sean\Pictures\digikam4.db" to a safe location and digiKam will create
a new database. Later you can use the migration tool in digiKam to copy the old
digikam4.db into the new one.

Maik
Comment 12 Maik Qualmann 2019-09-14 05:45:09 UTC

*** This bug has been marked as a duplicate of bug 411891 ***
Comment 13 caulier.gilles 2020-01-15 05:11:02 UTC
Today, next digiKam 7.0.0 beta2 64 bits pre-release AppImage bundle will be published with last Qt5.14 and QtWebEngine by default.

Please test and give us a feedback to see if problem remain on your computer.

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

Thanks in advance

Giles Caulier
Comment 14 caulier.gilles 2020-01-17 13:59:17 UTC
Fixed with last 7.0.0-beta2 pre release appimage.

Feel free to reopen if problem remain.

Gilles Caulier