[solved] Chromium and seccomp-bpf-helpers

stelinux

Hi everyone,
I would ask to all the people that use Chromium on amd64 if they have the error:

joecool · n00b Joined: 31 Aug 2004 Posts: 31

Thanks for this report. I was beginning to believe I was the only person with this issue. However, this isn't a fix. It's a workaround, and a bad one from a security standpoint.

If you're able to, please show me what research you've found. I found this link, but their conclusion was wrong: https://forums.gentoo.org/viewtopic-p-8207898.html (the bug report linked to is for a different syscall failure... but we're all facing syscall 0026 failures)

h017ah · n00b Joined: 18 Apr 2007 Posts: 46

any news on this? I also lately have to start chromium with --disable-seccomp-filter-sandbox on one of my computers (tested now with version 70.something) - maybe we lack some kernel options for seccomp or something?

stelinux · Posted: Tue Aug 28, 2018 11:25 pm Post subject:

Sorry for delay,
You are right about security so I choose to remove definitely chromium and to install google-chrome that do not have this problem.
Furthermore I use Falkon / qtwebengine-5.9.6 with QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu"

And, believe me, I love Linux but not the headache

_________________
stelinux on Ryzen 9 3900x on ROG Crosshair Hero VIII wifi 32GB G.Skill F4-3200C14D-16GFX CL16-16-16-39, 1.35 V
gentoo 17.1/no-multilib Sapphire Radeon RX 5700 XT 8G GDDR6 HDMI/TRIPLE DP OC W/ BP (UEFI)
openrc pipewire rocm

h017ah · n00b Joined: 18 Apr 2007 Posts: 46

Ahm. Well.

I just did a emerge -eav world on my system, with a newly installed gcc 8.2.0. That, combined with 4.18.5 kernel, and forcing chromium to compile with gcc, solved this issue for me.

It feels like an extremely overkill solution for this issue, but ... whatever works in the end. I have not been able to pinpoint exactly what fixed it, unfortunately...