Opera 125.0.5729.21 Stable update

[burnout426]

burnout426 Volunteer @Kilian01 last edited by

@Kilian01 Opera had a bug a bit ago *DNA-123982( where you had to call opera-stable instead of opera to launch Opera, but it was verified fixed in 124.0.5705.30. I'm guessing that an update to a build with the fix doesn't fix the issue.

What happens if you uninstall Opera and remove any traces of it (including "opera", "opera-stable" and any aliases) (you can keep your profile in ~/.config) and then install 125 fresh? Does that sort things out? If so, that might be what users have to do to fix things if they have the issue.

[filbo]

filbo @burnout426 last edited by

@burnout426: that was fixed in a way that should self-repair successfully on package update.

[filbo]

filbo @Kilian01 last edited by

@kilian01: I see 3 separate sets of issues in your log, unclear which of them might be relevant. First, easiest to fix, the sandbox binary has wrong permissions:

$ cd /usr/lib/x86_64-linux-gnu/opera-stable
$ sudo chown root opera_sandbox
$ sudo chmod 4755 opera_sandbox

Try after that.

But that is probably actually caused by the 2nd problem: the deb you're installing depends on 4 others, parts of your distro, which are not installed. Because of that it never finished installing, never ran /var/lib/dpkg/info/opera-stable.postinst which would have set up that setuid.

Package libqt5core5a is not installed.
Package libqt5gui5 is not installed.
Package libqt5gui5-gles is not installed.
Package libqt5widgets5 is not installed.
dpkg: error processing package opera-stable (--install):
dependency problems - leaving unconfigured

This not only leaves Opera unconfigured, but also missing libraries it depends on.

dpkg -i is the lowest level package installer. It is not meant to handle package dependencies; those belong to the higher APT subsystem. Try running instead: sudo apt install opera-stable_125.0.5729.21_amd64.deb. This will automatically pull in the packages it depends on.

The 3rd issue is a crash:

Trace/breakpoint trap (core dumped)

but that might be caused by the other two issues, so ignore it for now.

[filbo]

filbo @filbo last edited by

@filbo: argh, I failed at formatting the setuid instructions. But, you shouldn't really do that anyway. Just install properly with apt install and the postinst script will handle the setuid.

[metana]

metana @metana last edited by

@metana no one having the same issue ?

[Limon12324]

Limon12324 last edited by

Found a way to crash any user's Opera GX browser. See you in Bugcrowd Opera team

[MehrzadS]

MehrzadS last edited by

In Zorin OS the main menu is mispositioned.

[MehrzadS]

MehrzadS last edited by

In Zorin OS the side panel closes when I press Win+Space

[MehrzadS]

MehrzadS last edited by

In Zorin OS, when I want to attach a file in sidepanel telegram/whatsapp/... opera crashes (because the sidepanel window disapears and the file dialogue won't have a parent window)

[MehrzadS]

MehrzadS last edited by

Opera keeps wanting to update to 125.0.5729.21 but after every restart it's stuck to 125.0.5729.15. It doesn't upgrade.

[Kilian01]

Kilian01 @filbo last edited by

@filbo Thanks, I did notice that you can avoid or rather hide the problem with apt. The thing is the missing dependencies weren't critical in Opera 123. It still started at least. But Opera 124+ doesn't. If this is intentional (might be, only the Opera developer can answer that), then Opera shouldn't even install with the unmet dependencies. So there is a bug either way.

[MehrzadS]

MehrzadS @MehrzadS last edited by

@mehrzads: And why flatpak shows 125.0.5729.15 as the final version is beyond me.