The backtrace report a crash from QtWebEngine. It's a know problem relevant of Qt framework. Did you use a NVidia video card ?

The AppImage is not compiled with QtWebEngine, but QtWebKit instead. This is why it work well as QtWebKit do not have this kind of problem with video driver.

So typically, you must ask to Suse team to recompile digiKam with QtWebkit, not QtWebEngine, until this problem is fixed by Qt team.

Best

Gilles Caulier

What I'm wondering, I'm developing under openSUSE Tumbleweed. So I use the same packages. I have no problems at all with QWebEngine. Either the digiKam package is broken or it is due to the graphics hardware. I will install and test the official openSUSE digiKam package this evening. A mistake the user in openSUSE like to do is to mix packages from different sources (extras, unstable, etc.) Please also test this with your installation.

Maik

I can not reproduce a problem with the official digiKam-6.3.0 packages from openSUSE Tumbleweed. I have an AMD graphics card with "radeon" driver.

Which graphics card / driver do you use?
Check mixing of installed packages from different repositories.

Maik

Git commit d73a25ed14440af7aabcc161d3a26adfdb9dd52a by Maik Qualmann.
Committed on 20/09/2019 at 20:02.
Pushed by mqualmann into branch 'master'.

set QWebEngine settings after new page

M  +6    -6    core/app/views/stack/welcomepageview.cpp
M  +5    -5    core/utilities/geolocation/geoiface/widgets/htmlwidget_qwebengine.cpp

https://invent.kde.org/kde/digikam/commit/d73a25ed14440af7aabcc161d3a26adfdb9dd52a

Created attachment 122782 [details]
attachment-8114-0.html

 Yes, i am use a nvidia graphics card.
01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
i   | nvidia-computeG05                | NVIDIA driver for computing with GPGPU                             | Paket     
i+ | nvidia-gfxG05-kmp-default     | NVIDIA graphics driver kernel module for GeForce 600 series and -> | Paket     
i+ | nvidia-glG05                          | NVIDIA OpenGL libraries for OpenGL acceleration                    | Paket     
i+ | x11-video-nvidiaG05              | NVIDIA graphics driver for GeForce 600 series and newer            | Paket     




    Am Freitag, 20. September 2019, 22:03:46 MESZ hat Maik Qualmann <bugzilla_noreply@kde.org> Folgendes geschrieben:  
 
 https://bugs.kde.org/show_bug.cgi?id=412113

--- Comment #4 from Maik Qualmann <metzpinguin@gmail.com> ---
Git commit d73a25ed14440af7aabcc161d3a26adfdb9dd52a by Maik Qualmann.
Committed on 20/09/2019 at 20:02.
Pushed by mqualmann into branch 'master'.

set QWebEngine settings after new page

M  +6    -6    core/app/views/stack/welcomepageview.cpp
M  +5    -5  
core/utilities/geolocation/geoiface/widgets/htmlwidget_qwebengine.cpp

https://invent.kde.org/kde/digikam/commit/d73a25ed14440af7aabcc161d3a26adfdb9dd52a

Created attachment 123189 [details]
attachment-13243-0.html

 This is the answer from SuSE Support.

Fakt ist:
   
   - digiKam: <https://api.kde.org/extragear-api/gr...tml/index.html>

– Qt5::WebKitWidgets – zwingend erforderlich.
– Qt5::WebEngine – nicht vorgeschrieben …
   
   - openSUSE:

– libqt5-qtwebengine – steht für Tumbleweed und Leap zur Verfügung …
– libqt5-qtwebkit – AFAICS, nur der Quellcode steht zur Verfügung …
   
   - Plasma ab Version 5.6 hat gar keine Qt WebKit mehr …
   - Und, <https://news.opensuse.org/2018/10/17...5-12-and-more/>.

   The KDE team has decided to remove Qt Webkit from the default openSUSE installation. There should be minimal impact to users; the only exception is with Marble and Digikam. Those will not be installed by default anymore because they still depend on Qt Webkit, but they’re still available from YaST and zypper.  Scheinbar, eine Fehlermeldung ist nötig – <https://bugzilla.opensuse.org/>. 

    Am Freitag, 20. September 2019, 22:03:46 MESZ hat Maik Qualmann <bugzilla_noreply@kde.org> Folgendes geschrieben:  
 
 https://bugs.kde.org/show_bug.cgi?id=412113

--- Comment #4 from Maik Qualmann <metzpinguin@gmail.com> ---
Git commit d73a25ed14440af7aabcc161d3a26adfdb9dd52a by Maik Qualmann.
Committed on 20/09/2019 at 20:02.
Pushed by mqualmann into branch 'master'.

set QWebEngine settings after new page

M  +6    -6    core/app/views/stack/welcomepageview.cpp
M  +5    -5  
core/utilities/geolocation/geoiface/widgets/htmlwidget_qwebengine.cpp

https://invent.kde.org/kde/digikam/commit/d73a25ed14440af7aabcc161d3a26adfdb9dd52a

OpenSUSE Tumbleweed provides digikam-6.4.0, is the issue still to reproduce?

Maik

Hi,

Can you check if this problem still exist with last weekly bundle build of digiKam 7.0.0 available here:

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

Thanks in advance

Gilles Caulier

digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Thanks in advance

Gilles Caulier

*** Bug 425962 has been marked as a duplicate of this bug. ***

You wrote in bug 409175 that the problem with the AppImage does not occur. So it must be a package bug. There must be something wrong with your openSUSE Tumbleewed installation. I compile digiKam myself under this Linux version and have no problems.

Maik

Created attachment 131290 [details]
hehenberger.vcf

   Hello Maik,
   the digikam-7.0.0-beta2.appimage work fine, but the
   digikam-7.0.0-x86-64.appimage crashed.

   -- 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
   libnss3.so
   -- Preloading shared libs:
   :/usr/lib64/libudev.so.0:/tmp/.mount_digikaDgmNv9/usr/lib64/libnss3.so
   [4534:4534:0830/160330.381198:ERROR:zygote_host_impl_linux.cc(89)]
   Running as root without --no-sandbox is not supported. See
   https://crbug.com/638180.
   /tmp/.mount_digikaDgmNv9/AppRun: Zeile 157: 4534 Segmentation fault
   (Speicherabzug geschrieben) digikam $@

   digikam-7.1.0-20200826T123515-x86-64.appimage

   root@newlx:/wtmp->./digikam-7.1.0-20200826T123515-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
   libnss3.so
   libxcb-dri3.so.0
   -- Preloading shared libs:
   :/usr/lib64/libudev.so.0:/tmp/.mount_digikaJ8tsx8/usr/lib64/libnss3.so:/tmp/.mount_digikaJ8tsx8/usr/lib64/libxcb-dri3.so.0
   unknown: KCatalog being used without a Q*Application instance. Some
   translations won't work
   [7155:7155:0830/163734.371445:ERROR:zygote_host_impl_linux.cc(89)]
   Running as root without --no-sandbox is not supported. See
   https://crbug.com/638180.
   /tmp/.mount_digikaJ8tsx8/AppRun: Zeile 158: 7155 Segmentation fault
   (Speicherabzug geschrieben) digikam $@


   Thanks for your help






   On 30.08.20 07:58, Maik Qualmann wrote:

     https://bugs.kde.org/show_bug.cgi?id=412113          
     --- Comment #11 from Maik Qualmann      <metzpinguin@gmail.com> [1]      ---
     You wrote in bug 409175 that the problem with the AppImage does not occur. So
     it must be a package bug. There must be something wrong with your openSUSE
     Tumbleewed installation. I compile digiKam myself under this Linux version and
     have no problems.
     
     Maik


   

   1. mailto:metzpinguin@gmail.com

Pauli,

Never start AppImage with root account. Always use standard user account instead.

This can be dangerous with root, as it's the admin account which have all rights on all files from the system.

Gilles Caulier

   Hello,
   even if digikam is started with a different user, the appimage does
   not work.

   work@newlx:/u1/sonstiges>
   ./digikam-7.1.0-20200826T123515-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
   libnss3.so
   libxcb-dri3.so.0
   -- Preloading shared libs:
   :/usr/lib64/libudev.so.0:/tmp/.mount_digikaRXPoP9/usr/lib64/libnss3.so:/tmp/.mount_digikaRXPoP9/usr/lib64/libxcb-dri3.so.0
   unknown: KCatalog being used without a Q*Application instance. Some
   translations won't work
   Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified
   unknown: could not connect to display :0
   unknown: Could not load the Qt platform plugin "xcb" in "" even though
   it was found.
   unknown: This application failed to start because no Qt platform
   plugin could be initialized. Reinstalling the application may fix this
   problem.

   Available platform plugins are: eglfs, minimal, minimalegl, offscreen,
   vnc, wayland-egl, wayland, wayland-xcomposite-egl,
   wayland-xcomposite-glx, xcb.

   /tmp/.mount_digikaRXPoP9/AppRun: Zeile 158: 2780 Aborted
   (Speicherabzug geschrieben) digikam $@


   Thanks for your help







   On 30.08.20 16:49, bugzilla_noreply@kde.org[1] wrote:

     https://bugs.kde.org/show_bug.cgi?id=412113          
     --- Comment #13 from      caulier.gilles@gmail.com [2]      ---
     Pauli,
     
     Never start AppImage with root account. Always use standard user account
     instead.
     
     This can be dangerous with root, as it's the admin account which have all
     rights on all files from the system.
     
     Gilles Caulier


   

   1. mailto:bugzilla_noreply@kde.org
   2. mailto:caulier.gilles@gmail.com

No connection to display :0? What kind of graphics system do you use? Possibly Wayland?

Maik

Run the appimage file with "debug" argument to get a gdb backtrace of crash

   Hello Maik,
   sorry my mistake, user work has no X surface.
   My server runs completely as root user and a change
   I do not want to do.
   Is there an option to run digicam as root user ?






   On 30.08.20 17:28, Maik Qualmann wrote:

     https://bugs.kde.org/show_bug.cgi?id=412113          
     --- Comment #15 from Maik Qualmann      <metzpinguin@gmail.com> [1]      ---
     No connection to display :0? What kind of graphics system do you use? Possibly
     Wayland?
     
     Maik


   

   1. mailto:metzpinguin@gmail.com

   Hello,
   I hope this helps you.

   root@newlx:/wtmp->gdb
   digikam-7.1.0-20200826T123850-x86-64-debug.appimage
   GNU gdb (GDB; openSUSE Tumbleweed) 9.2
   Copyright (C) 2020 Free Software Foundation, Inc.
   License GPLv3+: GNU GPL version 3 or later
   <http://gnu.org/licenses/gpl.html>[1]
   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-suse-linux".
   Type "show configuration" for configuration details.
   For bug reporting instructions, please see:
   <http://bugs.opensuse.org/>[2].
   Find the GDB manual and other documentation resources online at:
   <http://www.gnu.org/software/gdb/documentation/>[3].

   For help, type "help".
   Type "apropos word" to search for commands related to "word"...
   Reading symbols from
   digikam-7.1.0-20200826T123850-x86-64-debug.appimage...
   (No debugging symbols found in
   digikam-7.1.0-20200826T123850-x86-64-debug.appimage)
   (gdb) r
   Starting program:
   /u1/wtmp/digikam-7.1.0-20200826T123850-x86-64-debug.appimage
   Missing separate debuginfos, use: zypper install
   glibc-debuginfo-2.31-6.3.x86_64
   [Thread debugging using libthread_db enabled]
   Using host libthread_db library "/lib64/libthread_db.so.1".
   [Detaching after fork from child process 23640]
   process 23634 is executing new program: /usr/bin/bash
   Missing separate debuginfos, use: zypper install
   libfuse2-debuginfo-2.9.9-1.2.x86_64 libz1-debuginfo-1.2.11-14.2.x86_64
   -- 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"'.
   [Detaching after fork from child process 23644]
   [Detaching after fork from child process 23645]
   [Detaching after fork from child process 23647]
   libudev.so.0
   [Detaching after fork from child process 23648]
   libnss3.so
   [Detaching after fork from child process 23649]
   libxcb-dri3.so.0
   [Detaching after fork from child process 23650]
   -- Preloading shared libs:
   :/usr/lib64/libudev.so.0:/tmp/.mount_digikattQJWh/usr/lib64/libnss3.so:/tmp/.mount_digikattQJWh/usr/lib64/libxcb-dri3.so.0
   [Detaching after fork from child process 23651]
   unknown: KCatalog being used without a Q*Application instance. Some
   translations won't work
   [23651:23651:0830/182855.853905:ERROR:zygote_host_impl_linux.cc(89)]
   Running as root without --no-sandbox is not supported. See
   https://crbug.com/638180.
   /tmp/.mount_digikattQJWh/AppRun: Zeile 158: 23651 Segmentation fault
   (Speicherabzug geschrieben) digikam $@
   [Inferior 1 (process 23634) exited with code 0213]
   Missing separate debuginfos, use: zypper install
   bash-debuginfo-5.0.18-1.2.x86_64
   (gdb) where
   No stack.
   (gdb)






   On 30.08.20 17:31, bugzilla_noreply@kde.org[4] wrote:

     https://bugs.kde.org/show_bug.cgi?id=412113          
     --- Comment #16 from      caulier.gilles@gmail.com [5]      ---
     Run the appimage file with "debug" argument to get a gdb backtrace of crash


   

   1. http://gnu.org/licenses/gpl.html
   2. http://bugs.opensuse.org/
   3. http://www.gnu.org/software/gdb/documentation/
   4. mailto:bugzilla_noreply@kde.org
   5. mailto:caulier.gilles@gmail.com

After installing the required debug rpm's.
The --no-sandbox option does not work.

Thanks for the help


root@newlx:/wtmp->gdb digikam-7.1.0-20200826T123850-x86-64-debug.appimage
GNU gdb (GDB; openSUSE Tumbleweed) 9.2
Copyright (C) 2020 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-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.

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-7.1.0-20200826T123850-x86-64-debug.appimage...
(No debugging symbols found in 
digikam-7.1.0-20200826T123850-x86-64-debug.appimage)
(gdb) r
Starting program: 
/u1/wtmp/digikam-7.1.0-20200826T123850-x86-64-debug.appimage
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[Detaching after fork from child process 25529]
process 25520 is executing new program: /usr/bin/bash
-- 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"'.
[Detaching after fork from child process 25533]
[Detaching after fork from child process 25534]
[Detaching after fork from child process 25536]
libudev.so.0
[Detaching after fork from child process 25537]
libnss3.so
[Detaching after fork from child process 25538]
libxcb-dri3.so.0
[Detaching after fork from child process 25539]
-- Preloading shared libs: 
:/usr/lib64/libudev.so.0:/tmp/.mount_digikaHgTC5T/usr/lib64/libnss3.so:/tmp/.mount_digikaHgTC5T/usr/lib64/libxcb-dri3.so.0
[Detaching after fork from child process 25540]
unknown: KCatalog being used without a Q*Application instance. Some 
translations won't work
[25540:25540:0830/184734.040762:ERROR:zygote_host_impl_linux.cc(89)] 
Running as root without --no-sandbox is not supported. See 
https://crbug.com/638180.
/tmp/.mount_digikaHgTC5T/AppRun: Zeile 158: 25540 Segmentation 
fault      (Speicherabzug geschrieben) digikam $@
[Inferior 1 (process 25520) exited with code 0213]
(gdb)


On 30.08.20 17:31, bugzilla_noreply@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=412113
>
> --- Comment #16 from caulier.gilles@gmail.com ---
> Run the appimage file with "debug" argument to get a gdb backtrace of crash
>

You need to add "debug" as an option to the AppImage start in order to run it in the internal debugger. After the crash don't forget "bt" + Enter for the backtrace.

Maik

Created attachment 131300 [details]
attachment-23468-0.html

 ry: zypper install -C "debuginfo(build-id)=e4b500d33ad8701cf4f0c9d058cd87f10b6b72c1"
Missing separate debuginfo for /tmp/.mount_digikat5zfRL/usr/lib/libxslt.so.1
Try: zypper install -C "debuginfo(build-id)=85cc4f3e5fef6564668a00fdbe9a7c14cdbad926"
[New Thread 0x7fffca787700 (LWP 6822)]
[New Thread 0x7fffb7547700 (LWP 6827)]
[6786:6786:0830/215343.525545:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
[Thread 0x7fffca787700 (LWP 6822) exited]
[Thread 0x7fffcaf88700 (LWP 6796) exited]

Thread 3 "Digikam::ScanCo" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffcb789700 (LWP 6795)]
0x00007ffff3c9a012 in QReadWriteLock::tryLockForWrite(int) () from /tmp/.mount_digikat5zfRL/usr/lib/libQt5Core.so.5
Missing separate debuginfos, use: zypper install libX11-6-debuginfo-1.6.9-2.2.x86_64 libasound2-debuginfo-1.2.3.2-328.4.x86_64 libbrotlicommon1-debuginfo-1.0.7-4.2.x86_64 libbrotlidec1-debuginfo-1.0.7-4.2.x86_64 libcom_err2-debuginfo-1.45.6-1.19.x86_64 libdrm2-debuginfo-2.4.102-1.2.x86_64 libexpat1-debuginfo-2.2.9-1.12.x86_64 libffi8-debuginfo-3.3.git30-1.13.x86_64 libfontconfig1-debuginfo-2.13.1-2.8.x86_64 libfreetype6-debuginfo-2.10.2-1.3.x86_64 libgcc_s1-debuginfo-10.2.1+git501-1.2.x86_64 libglib-2_0-0-debuginfo-2.64.4-1.2.x86_64 libglvnd-debuginfo-1.2.0-4.4.x86_64 libgpg-error0-debuginfo-1.38-1.3.x86_64 libjack0-debuginfo-1.9.14-117.6.x86_64 libp11-kit0-debuginfo-0.23.20-1.4.x86_64 libstdc++6-debuginfo-10.2.1+git501-1.2.x86_64 libusb-1_0-0-debuginfo-1.0.23-1.6.x86_64 libuuid1-debuginfo-2.35.1-2.3.x86_64 libxcb1-debuginfo-1.14-1.3.x86_64
(gdb) where
#0  0x00007ffff3c9a012 in QReadWriteLock::tryLockForWrite(int) ()
   from /tmp/.mount_digikat5zfRL/usr/lib/libQt5Core.so.5
#1  0x00007ffff78627ec in ?? () from /tmp/.mount_digikat5zfRL/usr/lib/libQt5Sql.so.5
#2  0x00007ffff73af86a in Digikam::DbEngineThreadData::closeDatabase (this=this@entry=0x7fffc4030040)
    at /b/dktemp/digikam-master/core/libs/database/engine/dbenginebackend.cpp:107
#3  0x00007ffff73af8ec in Digikam::DbEngineThreadData::~DbEngineThreadData (this=0x7fffc4030040, 
    __in_chrg=<optimized out>) at /b/dktemp/digikam-master/core/libs/database/engine/dbenginebackend.cpp:86
#4  0x00007ffff73b840e in qThreadStorage_deleteData<Digikam::DbEngineThreadData> (d=0x7fffc4030040)
    at ././/include/QtCore/qthreadstorage.h:92
#5  QThreadStorage<Digikam::DbEngineThreadData*>::deleteData (x=0x7fffc4030040)
    at ././/include/QtCore/qthreadstorage.h:135
#6  0x00007ffff3c9e052 in QThreadStorageData::finish(void**) () from /tmp/.mount_digikat5zfRL/usr/lib/libQt5Core.so.5
#7  0x00007ffff3c97852 in ?? () from /tmp/.mount_digikat5zfRL/usr/lib/libQt5Core.so.5
#8  0x00007ffff3c9833d in ?? () from /tmp/.mount_digikat5zfRL/usr/lib/libQt5Core.so.5
#9  0x00007ffff360ceaa in start_thread (arg=<optimized out>) at pthread_create.c:477
#10 0x00007ffff353caff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) 


    Am Sonntag, 30. August 2020, 21:45:00 MESZ hat Maik Qualmann <bugzilla_noreply@kde.org> Folgendes geschrieben:  
 
 https://bugs.kde.org/show_bug.cgi?id=412113

--- Comment #20 from Maik Qualmann <metzpinguin@gmail.com> ---
You need to add "debug" as an option to the AppImage start in order to run it
in the internal debugger. After the crash don't forget "bt" + Enter for the
backtrace.

Maik

I can reproduce your problem here under openSUSE when I try to start the AppImage as "root" user. You must not be a "root" user!

Maik

My compiled digiKam version doesn't run as "root" user either. Use a normal user account. I'm closing the bug now.

Maik

   Hello Maik
   is there a possibility for a root option.
   My workstation runs mostly under root and sometimes I know what I am
   doing.

   Thanks for your support and a wonderful software


   Mit freundlichen Grüßen

   nfslog


   Robert Hehenberger


   NFS Netzwerkfunksysteme GmbH


   Westach 12


   84424 Isen

   Telefon:

   Fax:

   Mobile:

   Web:

   Mail:

   UST-ID:

   HRB:

   08083 908 277-0

   08083 908 277-6

   0173 999 0 333

   www.nfsgmbh.de[1]

   hehenberger@nfsgmbh.de[2]

   DE 814 414 351

   157358 AG München

   On 31.08.20 21:03, Maik Qualmann wrote:

     https://bugs.kde.org/show_bug.cgi?id=412113          
     --- Comment #22 from Maik Qualmann      <metzpinguin@gmail.com> [3]      ---
     I can reproduce your problem here under openSUSE when I try to start the
     AppImage as "root" user. You must not be a "root" user!
     
     Maik


   

   1. http://www.nfsgmbh.de/
   2. mailto:hehenberger@nfsgmbh.de
   3. mailto:metzpinguin@gmail.com

I haven't really researched it yet. But due to the message that the application cannot be executed in the sandbox, it looks like openSUSE is starting unknown apps for "root" users in a sandbox. It is absolutely wrong to work as "root" user under a modern Linux, even if you know what you are doing.

Maik

The cause is the Chrome browser in digiKam. This refuses to start as "root" user. I don't know if we have the option to disable the sandbox in the Chrome browser, I think we shouldn't.

Maik

You can set an environment variable to force the start as "root" user:

export QTWEBENGINE_DISABLE_SANDBOX=1

I hope you know what you are doing...

Maik

   Hello Mike,
   on the chrome browser I can easily distinguish
   (I use firefox) but digikam would be very difficult for me. Maybe you
   will find a possibility after all.
   That would be worth a case of beer to me.
   Thanks for your help in advance


   Mit freundlichen Grüßen

   nfslog


   Robert Hehenberger


   NFS Netzwerkfunksysteme GmbH


   Westach 12


   84424 Isen

   Telefon:

   Fax:

   Mobile:

   Web:

   Mail:

   UST-ID:

   HRB:

   08083 908 277-0

   08083 908 277-6

   0173 999 0 333

   www.nfsgmbh.de[1]

   hehenberger@nfsgmbh.de[2]

   DE 814 414 351

   157358 AG München

   On 01.09.20 07:42, Maik Qualmann wrote:

     https://bugs.kde.org/show_bug.cgi?id=412113          
     --- Comment #26 from Maik Qualmann      <metzpinguin@gmail.com> [3]      ---
     The cause is the Chrome browser in digiKam. This refuses to start as "root"
     user. I don't know if we have the option to disable the sandbox in the Chrome
     browser, I think we shouldn't.
     
     Maik


   

   1. http://www.nfsgmbh.de/
   2. mailto:hehenberger@nfsgmbh.de
   3. mailto:metzpinguin@gmail.com

   Hello Mike,
   Looks good, do you have a paypal account ?


   Mit freundlichen Grüßen

   nfslog


   Robert Hehenberger


   NFS Netzwerkfunksysteme GmbH


   Westach 12


   84424 Isen

   Telefon:

   Fax:

   Mobile:

   Web:

   Mail:

   UST-ID:

   HRB:

   08083 908 277-0

   08083 908 277-6

   0173 999 0 333

   www.nfsgmbh.de[1]

   hehenberger@nfsgmbh.de[2]

   DE 814 414 351

   157358 AG München

   On 01.09.20 07:47, Maik Qualmann wrote:

     export QTWEBENGINE_DISABLE_SANDBOX=1   

   

   1. http://www.nfsgmbh.de/
   2. mailto:hehenberger@nfsgmbh.de

The browser engine "QWebEngine" used by digiKam is based on Chrome. You only have to set the environment variable (see Comment 27), then digiKam starts as "root" user.

Maik

Hi Pauli,

Thanks to support digiKam project. All is explained here:

 https://www.digikam.org/donate/

Best regards

Gilles Caulier