[Solved]Opera 66.0.3515.72-1 crashing without any extension or new installation

[pindos]

pindos last edited by

I have updated to 66.0.3515.103 some days ago. I experience no problems with it on LinuxMint 19.3 and Win10 machines. But I noticed that there is no such version on ftp.opera.com. Other machines running Windows 10 at my work don't find this update. They use 66.0.3515.95, and I get "Opera is up to date" message on them. May be the 103-version is buggy.

[l33t4opera]

l33t4opera @pindos last edited by

Hi @pindos, it looks to be the problem so far only for Arch Linux (and based on it other distros), with incompatible glibc version.

[zibi1981]

zibi1981 last edited by zibi1981

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.

[l33t4opera]

l33t4opera @zibi1981 last edited by

Hi @zibi1981, and what if you launch the Opera in a "normal" terminal session, and with the switch as follows: usr/bin/opera --disable-gpu-sandbox, does it change anything?

[l33t4opera]

l33t4opera @l33t4opera last edited by l33t4opera

@pindos The version is present on the ftp servers here, but it seems the issue is still not fixed in this one.

[zibi1981]

zibi1981 @l33t4opera last edited by

@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.

[l33t4opera]

l33t4opera @zibi1981 last edited by l33t4opera

@zibi1981 I see. I proposed it, because disabling the sandbox only for GPU looks to be a little safer - and only as a workaround to not having downgrading the glibc stuff, until the time the issue will be probably fixed in one of upcoming versions.

[arup65]

arup65 @zibi1981 last edited by

@zibi1981 make sure to enable Firejail system wide and also incorporate apparmor to make it bullet proof.

[pindos]

pindos @zibi1981 last edited by

@zibi1981 Sorry. I missed it. I looked for it at the end ftp list. Yes, the link is present there.

[zibi1981]

zibi1981 last edited by

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

[A Former User]

A Former User last edited by

I think you can use opera developer!

[minho]

minho last edited by

Opera 67 is released.
Is this problem solved?

[A Former User]

A Former User @minho last edited by

@minho said in Opera 66.0.3515.72-1 crashing without any extension or new installation:

Opera 67 is released.
Is this problem solved?

Yes

So far no Strike here

[2020-02-25T11:41:13-0300] [ALPM] upgraded opera-ffmpeg-codecs (79.0.3945.130-2 -> 80.0.3987.100-1)
[2020-02-25T11:41:13-0300] [ALPM] upgraded opera (66.0.3515.103-1 -> 67.0.3575.31-1)

Thanks for the solution sent through this update

[A Former User]

A Former User @minho last edited by

@minho said in Opera 66.0.3515.72-1 crashing without any extension or new installation:

Opera 67 is released.
Is this problem solved?

Yes. It is a home run for me!