04-24-2016, 04:26 AM
(04-23-2016, 02:32 PM)baryluk Wrote: It works!
(High CPU usage is mostly due to the fact that MATE system monitor is consuming quiet a bit of cpu for drawing stuff. When using top, chromium is using few % when idle basically)
Remember to run with:
$ chromium --disable-seccomp-filter-sandbox
(probably due to the bug in the old kernel, seccomp and seccomp filter is in 3.10.65 according to /proc/config.gz)
Packages:
http://repo.linaro.org/ubuntu/linaro-ove...m-browser/
Debian bug: https://bugs.debian.org/cgi-bin/bugrepor...799939#113
There should also be 49.0 in debian experimental, didn't checked it yet.
I can confirm this also works for chromium under Arch Linux. chromium --disable-seccomp-filter-sandbox fixes the awww snap error that occurs after starting chromium under arch.