Opera 109.0.5097.59 stable update
-
burnout426 Volunteer last edited by
@jedi-am said in Opera 109.0.5097.59 stable update:
where is changelog for this version.
Opera never posted one for .68.
Again in linux on snap version, bad release because i can not watch videos again. This is the second time, wtf.
I have chromium-ffmpeg snap package, it should be working.
This is known issue DNA-116350 and is being worked on. Versioning for it has to be bumped again. Hopefully the fix will be out soon.
-
jedi-am last edited by
@burnout426:
where is this DNA-116350 on a blog post ?What about other issue with white box showing around on right menu or similar ?
-
burnout426 Volunteer last edited by
@jedi-am said in Opera 109.0.5097.59 stable update:
where is this DNA-116350 on a blog post ?
It's not posted anywhere.
I guess there's a workaround though. You can do:
snap refresh chromium-ffmpeg --revision 37
to go back to the previous chromium-ffmpeg. This might break other snap apps that need the current 38 though, but it might solve it for Opera until the first Opera 110 snap comes out.
-
jedi-am last edited by
@burnout426:
thanks for the tips but it is better to not break others apps that depend on snap ffmpeg .
Any expected date when new version of opera will be released ? -
burnout426 Volunteer last edited by
@jedi-am said in Opera 109.0.5097.59 stable update:
Any expected date when new version of opera will be released ?
Not sure, but since 110 is in beta, I'm guessing it won't be too long before 110 hits stable where things should then work.
-
rick2 last edited by
@burnout426: thanks for your reply, sorry I didn't see it sooner.
Stil no .59, .68 nor .80 versions in flathub.org unfortunately
I know they recently revamped the process (security-wise) of uploading apps, so maybe there's some blocker?
-
rick2 last edited by
@burnout426 BTW, I wouldn't mind installing from the RPM repo but I need to have 2 Opera versions (Stable and Beta) installed at the same time, and the RPM versions conflict against each other due to including same-named files, eg:
Error: Error de prueba de transacción: el archivo /usr/lib/.build-id/62/67c27aeb53c29b0577749c6ebd79e0f1e8244a de la instalación de opera-stable-109.0.5097.80-0.x86_64 entra en conflicto con el archivo del paquete opera-beta-110.0.5130.17-0.x86_64
Error: Error de prueba de transacción: el archivo /usr/lib/.build-id/62/67c27aeb53c29b0577749c6ebd79e0f1e8244a de la instalación de opera-developer-111.0.5159.0-0.x86_64 entra en conflicto con el archivo del paquete opera-beta-110.0.5130.17-0.x86_64 el archivo /usr/lib/.build-id/67/00ff851e6aef8dc9be8a72cac3c90ad34c7f3c de la instalación de opera-developer-111.0.5159.0-0.x86_64 entra en conflicto con el archivo del paquete opera-beta-110.0.5130.17-0.x86_64
-
burnout426 Volunteer last edited by
@jedi-am Guess the maintainer of the chromium-ffmpeg snap reverted it back to 37 and it working on a new version that's like 38, but will also be compatible with Opera 109.
-
burnout426 Volunteer last edited by burnout426
@rick2 Maintainer said that according to Flatpak devs, detection of new updates is a little wonky for Flatpak packages right now (see https://github.com/flathub-infra/flatpak-external-data-checker/issues/416#issuecomment-2090071108), so the updates were not being detected automatically and he didn't notice himself that there were new updates. So, he's going to update the Flatpak to the latest manually for now (including libffmpeg from https://github.com/Ld-Hagen/fix-opera-linux-ffmpeg-widevine/releases in it).
According to https://github.com/flathub/com.opera.Opera, it looks like the changes might have already been made, but I didn't test anything personally.
-
rick2 last edited by
@burnout426 thanks for the info!
Yes, I already received Opera 109.0.5097.80 via flatpak a couple of days ago, even with the fix for using Plasma 6's kwallet.
And the libffmpeg update I noticed also. I usually overwrite it by hand and to update Opera I need to run
sudo flatpak repair
. This time it wasn't necessary, it seems. -