Created attachment 289933 [details] Konfiguration of affected kernel 5.8-rc3 With 5.8-rc3 I get seccomp crashes when trying to read mail: % kmail Use of deprecated not thread-safe setter, use setUrlRequestInterceptor instead. ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0072 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0072 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0072 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0072 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0072 KMail tries to start QtWebEngine repeatedly, but it does not work. Reverting back to 5.8-rc2 fixes the issue.
This is caused by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c15badbb7b20ccdbadf5da14e0a68fbad51015. Reverting the patch makes Chromium and related entities work correctly again.
Thanks, Michael. Another report linking to the same commit: Maxim Levitsky, Commit 'fs: Do not check if there is a fsnotify watcher on pseudo inodes' breaks chromium here https://lore.kernel.org/lkml/7b4aa1e985007c6d582fffe5e8435f8153e28e0f.camel@redhat.com/
Patch has been reverted in 5.8-rc4. Thus closing.