You are not logged in.
Hello,
After a full upgrade, qt5-webengine 5.15.2-5.0 crashes when attempting to render pages. glibc version is 2.33-3.3. Running qutebrowser, I get the following (the first 3 output lines appear even when qutebrowser is working properly):
$ qutebrowser
propsReply "Method \"GetAll\" with signature \"s\" on interface \"org.freedesktop.DBus.Properties\" doesn't exist\n"
nmReply "Method \"GetDevices\" with signature \"\" on interface \"org.freedesktop.NetworkManager\" doesn't exist\n"
"Object path cannot be empty"
Xlib: sequence lost (0x1022c > 0x22e) in reply type 0x0!
Xlib: sequence lost (0x1023f > 0x241) in reply type 0x0!
../../../../qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
Xlib: sequence lost (0x10253 > 0x255) in reply type 0x0!
Xlib: sequence lost (0x102dc > 0x2de) in reply type 0x0!
../../../../qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
17:43:50 ERROR: Renderer process crashed
Xlib: sequence lost (0x10348 > 0x34a) in reply type 0x0!
../../../../qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
17:43:52 ERROR: Renderer process crashed
Xlib: sequence lost (0x1039d > 0x39f) in reply type 0x0!
../../../../qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
../../../../qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
../../../../qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
17:43:53 ERROR: Renderer process crashed
17:43:55 ERROR: Renderer process crashed
../../../../qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
Xlib: sequence lost (0x10410 > 0x412) in reply type 0x0!
17:43:56 ERROR: Renderer process crashedThis is similar to another recent crash, with threads at [1][2]. That problem affected Chromium as well. I haven't seen a thread about Chromium breaking --- if this is unique to qt5-webengine and doesn't affect Chromium, I imagine it will be harder to find a patch. Unfortunately I'm not skilled enough to write one myself. I'll poke around and try for a bit anyway, but I don't expect to be able to fix it.
I know the glibc upgrade broke some things, particularly related to seccomp. Sorry to be adding this to that list. I hope that this will not be too much work to look into. Is this the same issue that's talked about in the recent announcement [3]?
[1]: https://bbs.archlinux32.org/viewtopic.php?id=2957
[2]: https://bbs.archlinux32.org/viewtopic.php?id=2897
[3]: https://bbs.archlinux32.org/viewtopic.php?id=3049
Last edited by jetfrog28 (2021-02-14 00:30:20)
Offline
Hmm, it appears that upstream Arch Linux patches qt5-webengine over a problem with glibc [4]. The patch does change the particular file named in the crash output. Perhaps it's related.
Offline
Are you using pentium 4 packages or something older? glibc 2.33 is noted to break lots of things according to this bug
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Sorry for the oversight. I'm using pentium 4 packages on the testing repos.
seccomp is part of the kernel, correct? So fixing this would either mean patching qt5-webengine or the kernel? I know there is also libseccomp, but it doesn't look like qt5-webengine uses it to me (aside from a dependency chain through file, which seems to be working properly on my system).
Offline
../../../../qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
This is not a kernel thing. chromium's sandbox fails executing some functions which are either not allowed in the sandbox to
be executed (so rules are missing there) or libseccomp doesn't know about them (yet).
The chromium codebase is copied all over the place instead of using a shared library, so these bugs appear in
all frameworks using the web engine. I didn't have time to look at chromium yet, because that's the place
where seccomp fixes usually appear first (or I have to do them myself first).
libsecomp itself doesn't learn automatically about new 32-syscalls, they also have to be added there first.
Offline
Thank you. I will keep reading on seccomp rules. Hopefully I will eventually be able to help patch problems like this.
Offline