Opera 124.0.5705.42 Stable update

[Scrofa]

Scrofa last edited by

After the 124.0.5705.42 update I am unable to even open Opera in Ubuntu. Fix this.

[ironbone]

ironbone last edited by

The snap opera version does not work with Wayland on Ubuntu

[ironbone]

ironbone @Scrofa last edited by

@scrofa: try as a temporary solution
opera --ozone-platform=x11

[Scrofa]

Scrofa @ironbone last edited by

@ironbone Thanks. It opens with that command but how can I keep it opened without closing the terminal?

[lfr1138]

lfr1138 @TheLamer last edited by

@TheLamer I am also experiencing this on Linux Mint 22.1. After uninstalling and attempting to reinstall from the downloaded .deb I see a message saying "Dependency is not satisfiable: libglib2.0-0(>=2.39.4)" and cannot install. A search of my installed packages yields:
"ii libglib2.0-0t64:amd64 2.80.0-6ubuntu3.4 amd64 GLib library of C routines"

Clearly multiple things are amiss with this .deb installer.

[filbo]

filbo @Opera-QA-Team last edited by

@opera-qa-team: same thing as @thelamer

The Linux APT .deb for opera-stable (specifically) is failing on install due to:

update-alternatives --install /usr/bin/x-www-browser x-www-browser /usr/bin/opera-stable 120 \                                                                  --slave /usr/share/man/man1/x-www-browser.1.gz x-www-browser.1.gz /usr/share/man/man1/opera-stable.1.gz                                         update-alternatives --install /usr/bin/gnome-www-browser gnome-www-browser /usr/bin/opera-stable 120 \                                                          --slave /usr/share/man/man1/gnome-www-browser.1.gz gnome-www-browser.1.gz /usr/share/man/man1/opera-stable.1.gz

-- which tries to link /usr/bin/opera-stable as /usr/bin/{x,gnome}-www-browser. Since the binary is /usr/bin/opera (sans -stable), this fails.

I note that it fails despite the priority 120 being lower than other choices (which means it will never in fact need to follow the path you've supplied). This seems like a tiny bug in update-alternatives(1), fwiw.

This should be fixed by changing the code to tell it to link /usr/bin/opera. You could also actually rename the binary, but if you do that, there will be many other changes elsewhere in your packaging, so I wouldn't go that way.

Meanwhile, your code also has a few other anomalies in this area. The postinst scripts for opera-developer, opera-beta, and opera-stable all give the same priority of 120. Other browsers give a higher priority to their 'stable' branch and successively lower for less stable branches.

And you instruct it to link man pages which do not in fact exist. This apparently doesn't bother update-alternatives even if your candidate is the winner, oddly enough.

[filbo]

filbo @filbo last edited by

A simple workaround for this install issue: cd /usr/bin; sudo ln -is opera opera-stable.

This can be done before the install; or after a failed / partial install. Then run apt reinstall opera-stable to finish.

[Opera-QA-Team]

Opera-QA-Team Opera @Urby938 last edited by

@urby938: Hi, thanks for pointing this out. Are they working for you in another browser? I checked and cannot trigger it in Chrome. Could you check?

[thelittlebrowserthatcould]

thelittlebrowserthatcould @Kilian01 last edited by

@kilian01: fixed, when I booted up at 07:45 UTC, 2025-11-26.

[thelittlebrowserthatcould]

thelittlebrowserthatcould last edited by

Now that my Linux version has successfully installed, I did have to update the location for the lib_extra folder.
My libffmpegDOTso from September still seemed OK, but I updated it anyway, from: https://github.com/Ld-Hagen/fix-opera-linux-ffmpeg-widevine/releases/latest

[ironbone]

ironbone @Scrofa last edited by

@scrofa: I have change for this moment, on the login page, Wayland to x11, to use it. Then opera will start without problems