 I think qtbase can be hinted, as the notepadqq test fail is glibc's fault
 oooh. it is crashing webengine!
 but only on armhf
 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
[12:12] <fvogt> Sounds like one of the time64 syscalls
[12:13] <fvogt> https://build.opensuse.org/package/view_file/KDE:Qt:5.15/libqt5-qtwebengine/sandbox-statx-futex_time64.patch?expand=1
[12:14] <fvogt> Upstream chromium doesn't seem to care about 32bit at all
 thanks!
 @mitya57 ^
 We have the time64 patch too, but it's for 0403 and 0407 syscalls.
 Looks like we need this one: https://github.com/archlinux/svntogit-packages/blob/packages/qt5-webengine/trunk/qt5-webengine-glibc-2.33.patch (re @lubuntu_bot: (irc) <fvogt> https://build.opensuse.org/package/view_file/KDE:Qt:5.15/libqt5-qtwebengine/sandbox-statx-futex_time64.patch?expand=1)
 I will look at it later, not much time today.
[14:52] <fvogt> mitya57: 0422 is futex_time64
[14:54] <fvogt> So what I linked is definitely what you need for this particular error
[14:54] <mitya57> fvogt: ah, indeed you are right. Thanks!