Created attachment 144405 [details] Empty login window to onedrive SUMMARY When trying to export to Onedrive, an empty window opens (see attachment). Therefore it is not possible to log in into Onedrive account. Besides that, if I close that empty window and click on "Change account" of the "Export to Onedrive" window, Digikam crashes. See logs attached SYSTEM Fedora 35 Appimage digiKam-7.3.0-x86-64.appimage Note: I also tried with latest digiKam-7.4.0-20211209T121203-x86-64.appimage -> but it crashes immediately: $ ./digiKam-7.4.0-20211209T121203-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. -- to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0 digikam: /tmp/.mount_digiKaJSufa6/usr/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libk5crypto.so.3) I already had similar problem with Onedrive (see bug #401377) but it was solved 2 years ago.
Created attachment 144406 [details] Digikam 7.3.0 crash log When I click on "Change account" (see at the end of attached file): unknown: UNLINK to Onedrive /tmp/.mount_digiKaO9UeHb/AppRun: line 172: 12759 Segmentation fault (core dumped) digikam $@
additional info: digikam appimage 7.4.0 starts with following command line: LD_PRELOAD=/usr/lib64/libssl.so.1.1:/usr/lib64/libcrypto.so.1.1 ./digiKam-7.4.0-20211209T121203-x86-64.appimage But then the behaviour is excatly the same than 7.3.0 (empty log in window and crash if I click on "Change account"). So problem reproducible with 7.3.0 et 7.4.0.
Please run the AppImage binary with the "debug" argument. This will run digiKam in the gdb debugger. When it crash, a prompt will appear. Enter "bt" to get a back-trace. To quit, enter "q". Gilles Caulier
The problem is known and will not work with the AppImage either. OnDrive does not work with the outdated QWebKit browser. Here native digiKam with QWebEngine works. Maik
*** This bug has been marked as a duplicate of bug 433219 ***
(In reply to Maik Qualmann from comment #4) > The problem is known and will not work with the AppImage either. OnDrive > does not work with the outdated QWebKit browser. Here native digiKam with > QWebEngine works. > > Maik How do I know if I have a QWebKit or a QWebEngine version of digikam ? I think I have QWebEngine because in "Help > Components Information" I have: digikam version 7.3.0 ... Qt: 5.14.2 Qt WebEngine support: Yes ... So Onedrive should work isn't ?
Yes, Help Components Info dialog show this information. And yes you use QtWebEngine (Chromium in fact)
(In reply to caulier.gilles from comment #7) > Yes, Help Components Info dialog show this information. And yes you use > QtWebEngine (Chromium in fact) Thanks Gilles. But then I don't understand Maik's comment: > OnDrive does not work with the outdated QWebKit browser. Here native digiKam with QWebEngine works. As I don't use QWebKit but QtWebEngine, Onedrive should work on my machine ?
On AppImage for Linux, QtWebEngine is always used, as under MacOS. Only Windows use QtWebKit, as Chromium code cannot be cross compiled yet. QtWebEngine is the more updated than QtWebkit, about web service security issues. It preferable to use webengine, but we still to use Qt 5.15.2, where last LTS version is 5.15.7, but this version is not published as open source. To be updated, we need to switch to Qt 6.2, but not all the DK code and dependencies are not yet ported. To resume : perhaps an LTS update of QtWebEngine is necessary to solve this issue. Gilles Caulier
Fixed with bug 433219