- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Packages → Packages: Stable
- Assigned To No-one
- Operating System pentium4
- Severity Low
- Priority Medium
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: Arch Linux 32
Opened by Andreas Baumann - 27.02.2020
Last edited by Andreas Baumann - 25.04.2020
Opened by Andreas Baumann - 27.02.2020
Last edited by Andreas Baumann - 25.04.2020
FS#105 - chromium crash in blocked syscalls (libseccomp)
chromium apparently also has trouble in some seccomp jailing:
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 [1201:1210:0227/131355.020958:FATAL:gpu_data_manager_impl_private.cc(990)] The display compositor is frequently crashing. Goodbye. [1]+ Trace/breakpoint trap (core dumped) chromium
Closed by Andreas Baumann
25.04.2020 11:36
Reason for closing: Fixed
Additional comments about closing:
25.04.2020 11:36
Reason for closing: Fixed
Additional comments about closing:
See https://bbs.arc hlinux32.org/viewtopic.php?pid=7069#p706 9
In the GUI you just get the usual "Aw, Snap!" in a tab.
version 80.0.3987.122 also shows this problem in testing after a rebuild, so it needs
patching the seccomp handling in chromium itself..
firefox also shows seccomp sandbox violations with syscall 403, presumably the same lack
of 32-bit seccomp rules also in firefox. There though the content of the page is shown
(at least for simple examples).