Hi Denys,
On Wed, 06 Oct 2021 19:19:56 -0400 Denys Dmytriyenko <[email protected]> wrote:
> On Wed, Oct 06, 2021 at 04:54:54PM -0400, Vivien Didelot wrote:
> > Instead of maintaining an inappropriate hack on qtwebengine to disable
> > seccomp filter sandbox, export the corresponding chromium flag in
> > the QTWEBENGINE_CHROMIUM_FLAGS environment variable.
> >
> > Signed-off-by: Vivien Didelot <[email protected]>
> > ---
> > .../qt5/qtbase-conf/ti33x/qt_env.sh | 5 +++
> > ...-disable-SECCOMP-BPF-Sandbox-at-star.patch | 32 -------------------
> > .../recipes-qt/qt5/qtwebengine_git.bbappend | 4 ---
> > 3 files changed, 5 insertions(+), 36 deletions(-)
> > delete mode 100644
> > meta-arago-distro/recipes-qt/qt5/qtwebengine/0003-qtwebengine-HACK-disable-SECCOMP-BPF-Sandbox-at-star.patch
> >
> > diff --git a/meta-arago-distro/recipes-qt/qt5/qtbase-conf/ti33x/qt_env.sh
> > b/meta-arago-distro/recipes-qt/qt5/qtbase-conf/ti33x/qt_env.sh
> > index 29fa2969..96526393 100644
> > --- a/meta-arago-distro/recipes-qt/qt5/qtbase-conf/ti33x/qt_env.sh
> > +++ b/meta-arago-distro/recipes-qt/qt5/qtbase-conf/ti33x/qt_env.sh
> > @@ -7,3 +7,8 @@ export QT_QPA_EGLFS_KMS_CONFIG=/etc/qt5/eglfs_kms_cfg.json
> > export QT_QPA_EGLFS_INTEGRATION=eglfs_kms
> > export QT_QPA_EGLFS_ALWAYS_SET_MODE=1
> > export QT_WAYLAND_SHELL_INTEGRATION=wl-shell
> > +
> > +# SECCOMP-BPF Sandbox does not work due to unexpected FUTEX_UNLOCK_PI call
> > +# from the pthread implementation. Disable this feature temporarily until
> > +# those issues are resolved.
> > +export QTWEBENGINE_CHROMIUM_FLAGS="--disable-seccomp-filter-sandbox"
>
> Why is this only done for ti33x platform? What about other platforms?
Good catch! Should I bbappend the qtwebengine recipe instead to deploy
a new qtwebengine_env.sh file containing QTWEBENGINE_CHROMIUM_FLAGS?
Thanks,
Vivien
_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
