Update to Chromium 136 – Vivaldi Browser snapshot 3679.3

npro

Everything normal on Linux-land...

Linu74

@Thot said in Update to Chromium 136 – Vivaldi Browser snapshot 3678.3:

@Linu74 Is this with extensions? For me the console does not issue warnings. I have no extensions and Vivaldi starts and works fine till now.

@Thot with Extensions. I pushed the Automatic Update when it comes up and doesn't read the Post before the Update

How can I start the Snapshot on MacOS without Extensions?

Linu74

mib2berlin

@Linu74
Hi, the command is disable-extensions but I have no idea how to add it to open Vivaldi with it on MacOS.

Linu74

@mib2berlin said in Update to Chromium 136 – Vivaldi Browser snapshot 3678.3:

@Linu74
Hi, the command is disable-extensions but I have no idea how to add it to open Vivaldi with it on MacOS.

It is

open /Applications/Vivaldi\ Snapshot.app --args --disable-extensions

Linu74

npro

@MuscleFortune That's the way it goes bro . Welcome, btw.

PNNL

Reinstalled the previous version....this one doesn't start up on my system .... nice new installer though when installing the full version download

Vivaldi 7.4.3671.3 (Officiële build) (In afwachting van update 7.4.3678.3) (32-bits)
Revisie 3a863f57b5de5c97834577463e4586fc8c9a0b37
Besturingssysteem Windows 10 Version 22H2 (Build 19045.2965)
JavaScript V8 13.4.114.21
Gebruikersagent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36

nutcracker

Vivaldi no more! Using Edge to write this. Complete disaster!
PS The browser is not loading at all! Tried to install the previous snapshot and the installer refused. How can I do it? I'm completely dependent on Vivaldi
PS I succeeded in opening Vivaldi without extensions

npro

@nutcracker Or you can use Linux + Vivaldi

mib2berlin

@npro
No issues here either.
Do you use V2 extensions?

Ruarí

@Pesala Try running with --disable-extensions

AltCode

@MuscleFortune Not really. Vivaldi follows the Extended Stable Release (ESR) channel. In a nutshell, this means the only major Chromium updates Vivaldi will receive are the even-numbered ones because the ESR channel is updated every 8 weeks, as opposed to every 4 weeks like the stable channel.

Ruarí

@iosbeta: Try running with --disable-extensions

Ruarí

@nutcracker: Never downgrade a profile to a lower chromium version. You should have a backup of your profile, if you are using snapshots. If you are not backing up and you cannot afford to lose access to the snapshot, you should be running stable and NOT snapshots at all.

This kind of thing is entirely possible on snapshots and should be expected to happen from time to time. Snapshots are for testing. They are not a supported release stream.

Ruarí

Could those of you who are experiencing crashes please log a bug and upload those crashes to the bug repot. Thank you.

Since there appears to still be a crash on start for some users, I will disable autoupdates to this snapshot. If you want to test it, backup your user data directory and then download and install the update manually. Thanks for the testing!

DoctorG

Hardware Acceleration fail with Video Decoding on Windows 11 Pro 23H2 with some NVidia drivers.

Regression was reported to Vivaldi bug tracker as VB-116704 "HTML5 video does not start"
and to Chromium bug tracker as https://issues.chromium.org/issues/415370683

PNNL

@ruarí: The anonymous crashreport sent automatically isn't sufficiënt ?

yngve

@PNNL No, because 1) we would not know which report is yours (it is anonymous, after all), and 2) we would not know details about what what going on when the crash happened.

PNNL

@yngve: OK clear

PNNL

@ruarí, @yngve: filed a crashreport.cab

Pathduck

@Ruarí Interestingly, I have two Mv2 extensions, and after the update it failed twice to start. Started on the third attempt. Might be magical thinking but it kind of seems related if the Mv2 extension warnings are involved.

Anyway, after launching properly I went to chrome://flags and disabled the following flags:
chrome://flags/#extension-manifest-v2-deprecation-warning
chrome://flags/#extension-manifest-v2-deprecation-disabled
chrome://flags/#extension-manifest-v2-deprecation-unsupported

It now seems to launch properly.