Opera 125.0.5729.21 Stable update

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

[Opera-QA-Team]

Opera-QA-Team Opera @Scrofa last edited by

@scrofa: Hello, we already fixed the bug, please keep an eye on updates.

[rick2]

rick2 @MehrzadS last edited by

@MehrzadS the Opera flatpak is a community maintained package, Opera the company is not involved in updating it AFAIK.
At least that's what they told me a couple years ago and why I switched to using the RPM repositories instead.

[filbo]

filbo @Kilian01 last edited by

@kilian01: no, you are misusing the packaging system. dpkg -i will install any package regardless of whether its dependencies are met. That is its role. apt et al are in charge of the higher level, including paying attention to dependencies. It is like... dpkg -i is you with a screwdriver and some random memory DIMMs, clicking then into your motherboard without checking for compatibility. While apt is you using a tool like pcpartspicker or paying a store to install RAM they've selected as compatible with your system. You can download any .deb from your OS's repo with apt download name-of-package, then install it with dpkg -i name-of-package_version_you_received.deb -- and the resulting installed package will fail in similar ways if you didn't grab its dependencies. The OS's packages -- and Opera -- have met their responsibility by recording those dependencies in the .deb metadata. apt implements paying attention to them. dpkg is a more internal tool and it has to allow installing packages without their dependencies (otherwise some early stages of system install could not work, as the most basic packages circularly depend on each other).

[Opera-QA-Team]

Opera-QA-Team Opera @ironbone last edited by

@ironbone: Hi what issues are you mentioning here?

[metana]

metana @metana last edited by

@metana
@Opera-QA-Team could you plz check this out?