Opera 124.0.5705.42 Stable update

ManagerBOSS

ManagerBOSS

After the latest browser update to version 124.0.5705.42, the pre-filled login feature stopped working. I have my logins saved in the browser and I haven't made any changes there. However, now when I want to log in to a URL where I have my login details saved, neither the login nor the password are pre-filled as they used to be, and what's more, when I enter my login, the password is not automatically filled in either. When I go to a specific URL, the key is missing in the top right corner, even though the URL is in the list of saved logins. Please note that this mainly concerns URLs that contain IP addresses, e.g., https://192.168.1.2.

TheLamer

TheLamer @Opera-QA-Team

@Opera-QA-Team

The deb is busted since this release:

11.74 Setting up opera-stable (124.0.5705.42) ...
11.82 update-alternatives: error: alternative path /usr/bin/opera-stable doesn't exist
11.85 dpkg: error processing package opera-stable (--configure):
11.85  installed opera-stable package post-installation script subprocess returned error exit status 2

Tested on bookworm, Trixie, and Noble. Related to renaming the package but the deb contents do not contain that bin.

./bin
./bin/opera

The problem is specifically in your postinst in the deb:

EOF
            chmod 755 /etc/cron.daily/opera-browser
            # Run once now to add Opera's pgp key to apt's keyring
            /etc/cron.daily/opera-browser > /dev/null 2>&1


        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
        ;;

esac

Because the name was changed your deb build env looks like it templates that name into the post install hooks and every deb is failing now.

Kilian01

Kilian01

Linux release is now available but fails to properly install. Please fix this immediately. I may remind you that this is calld stable, not beta or developer.

Scrofa

Scrofa

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

ironbone

ironbone

The snap opera version does not work with Wayland on Ubuntu

ironbone

ironbone @Scrofa

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

Scrofa

Scrofa @ironbone

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

lfr1138

lfr1138 @TheLamer

@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

@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

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.