@krysys2008 Running Opera with "--disable-seccomp-filter-sandbox" switch didn't help in my case.

@edsonmartim No they didn't. This version of Vivaldi is still crashing on my fully updated Arch Linux.

@arup65 Opera, Vivaldi and Chromium - all three still crashing on up-to-date Arch.

Well...Opera is crashing again, this time with another problem

firejail opera --disable-seccomp-filter-sandbox
Reading profile /home/zbyszek/.config/firejail/opera.profile
Reading profile /etc/firejail/chromium-common.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-exec.inc
Reading profile /etc/firejail/disable-interpreters.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-common.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Parent pid 2184, child pid 2185
Error: invalid whitelist path /home/zbyszek/.config/opera
Error: proc 2184 cannot sync with peer: unexpected EOF
Peer 2185 unexpectedly exited with status 1

@l33t4opera Opera version 66.0.3515.103 is not fixed - that's for sure. Only running with --disable-seccomp-filter-sandbox switch does the job, but to prevail security vulnerabilities I use Firejail, as advised by many people.

The other option - running Opera with --disable-gpu-sandbox also seems to do the job.

On Arch installing Firejail from Community repository

sudo pacman -S firejail

and then running Opera with

firejail opera --disable-seccomp-filter-sandbox

seems to do the job for now, as a workaround.

Opera still freezes on my system if not started with "--disable-seccomp-filter-sandbox" option. But when I want to add some more security to it using Firejail and AppArmor, Opera is not saving any settings! Every start gives me a welcome window and I have to reconfigure it again. I don't have the time and patience and I've switched to Vivaldi for now. It works perfectly with

firejail --apparmor /usr/bin/vivaldi-stable --disable-seccomp-filter-sandbox %U

@joe232 It doesn't seem to be laggy on Vivaldi/Arch (up-to-date) run with

firejail --apparmor /usr/bin/vivaldi-stable --disable-seccomp-filter-sandbox %U

Well...Opera is crashing again, this time with another problem

firejail opera --disable-seccomp-filter-sandbox
Reading profile /home/zbyszek/.config/firejail/opera.profile
Reading profile /etc/firejail/chromium-common.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-exec.inc
Reading profile /etc/firejail/disable-interpreters.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-common.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Parent pid 2184, child pid 2185
Error: invalid whitelist path /home/zbyszek/.config/opera
Error: proc 2184 cannot sync with peer: unexpected EOF
Peer 2185 unexpectedly exited with status 1

@l33t4opera Opera version 66.0.3515.103 is not fixed - that's for sure. Only running with --disable-seccomp-filter-sandbox switch does the job, but to prevail security vulnerabilities I use Firejail, as advised by many people.

The other option - running Opera with --disable-gpu-sandbox also seems to do the job.

On Arch installing Firejail from Community repository

sudo pacman -S firejail

and then running Opera with

firejail opera --disable-seccomp-filter-sandbox

seems to do the job for now, as a workaround.

@itexstar Clearing cache didn't help.

@arup65 Opera, Vivaldi and Chromium - all three still crashing on up-to-date Arch.

@itexstar Vivaldi 2.11.1811.38 (Stable channel) (64-bit) is crashing on my up-to-date Arch.

@krysys2008 Running Opera with "--disable-seccomp-filter-sandbox" switch didn't help in my case.

@edsonmartim No they didn't. This version of Vivaldi is still crashing on my fully updated Arch Linux.