From ae74897d321c65aca844b23e4ae780fdd915185f Mon Sep 17 00:00:00 2001 From: Patrick J Volkerding Date: Wed, 16 Mar 2022 01:46:29 +0000 Subject: Wed Mar 16 01:46:29 UTC 2022 l/jasper-3.0.3-x86_64-1.txz: Upgraded. l/qt5-5.15.3_20220312_33a3f16f-x86_64-1.txz: Upgraded. If a 32-bit userspace is detected, then: export QTWEBENGINE_CHROMIUM_FLAGS="--disable-seccomp-filter-sandbox" This works around crashes occuring with 32-bit QtWebEngine applications. Thanks to alienBOB. n/krb5-1.19.3-x86_64-1.txz: Upgraded. n/samba-4.15.6-x86_64-1.txz: Upgraded. n/stunnel-5.63-x86_64-1.txz: Upgraded. --- source/l/qt5/profile.d/qt5.csh | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'source/l/qt5/profile.d/qt5.csh') diff --git a/source/l/qt5/profile.d/qt5.csh b/source/l/qt5/profile.d/qt5.csh index ec1ecd9be..0c3f10d42 100644 --- a/source/l/qt5/profile.d/qt5.csh +++ b/source/l/qt5/profile.d/qt5.csh @@ -15,3 +15,13 @@ if ( ! $?QT5DIR ) then endif endif set path = ( $path $QT5DIR/bin ) +# Unfortunately Chromium and derived projects (including QtWebEngine) seem +# to be suffering some bitrot when it comes to 32-bit support, so we are +# forced to disable the seccomp filter sandbox on 32-bit or else all of these +# applications crash. If anyone has a patch that gets these things running on +# 32-bit without this workaround, please let volkerdi or alienBOB know, or +# post your solution on LQ. Thanks. :-) +file /bin/cat | grep -wq 32-bit +if ( "$?" == "0" ) then + setenv QTWEBENGINE_CHROMIUM_FLAGS="--disable-seccomp-filter-sandbox" +endif -- cgit v1.2.3-80-g2a13