https://bugs.kde.org/show_bug.cgi?id=457662
--- Comment #4 from antikapitali...@pobox.sk --- QTWEBENGINE_DISABLE_SANDBOX=1 fixed it for me. Alright, you can close it. At first, I was perplexed because it was crashing all the time but often at different places. So i rebuilt digiKam with almost everything turned off, then it began crashing rather consistently at the same place. And then I noticed the message that it did not like running as UID=0 (root) without --no-sandbox. Thus, QtWebEngine was exiting and letting the rest of digiKam implode. At first it was crashing at seemingly random places; digKam being multithreaded, the first victim was essentially a random thread that wanted to have something to do with QtWebEngine, which had crapped out. It is broken by design and digiKam is its innocent victim. I am awfully sorry to have wasted your time. It has been my fault all along. -- You are receiving this mail because: You are watching all bug changes.