Upgrade to Chromium 114 – Vivaldi Browser snapshot 3023.3
-
@mib2berlin said in Upgrade to Chromium 114 – Vivaldi Browser snapshot 3023.3:
which sleep mode did you use?
I'm not sure... The selection from the Apple Menu and the result of inattention -after the screensaver's run it's course- both cause the issue.
Can you read the screenshot from my Energy Saver panel?
-
@OakdaleFTL
AH, I am sorry, forgot you are on MacOS, this is completely different to Windows/Linux Hibernate/Sleep.
This looks like a power save mode if you on Batterie, I always disable this on Windows if I am connected to a power supply.Cheers, mib
-
@mib2berlin Battery? My machine is a desktop...
I let it sleep when I'm not using it; restart it at least once a month, to let the OS check on things!
-
did big albeit routine update of my system, many new pkg versions [including mesa, chromium (to 114), vulkan-intel, intel-media-sdk, glib2]. decided to try this surly snappie again. still fails at launch, still before UI, but now with different error/s than originally [now a coredump]:
meee@arch[~] 18:23:16 Sun May 28 $> /opt/vivaldi-snapshot/vivaldi-snapshot --disable-gpu --profile-directory="NewTestProfile" [8606:8606:0528/182526.417723:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled. MESA-INTEL: warning: Haswell Vulkan support is incomplete [8606:8606:0528/182526.570513:ERROR:wayland_event_watcher.cc(39)] libwayland: xdg_surface@41: error -1: invalid window geometry size (0x0) [0528/182526.577907:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0528/182526.578418:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0528/182526.578530:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0528/182526.578606:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0528/182526.581096:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0528/182526.581821:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0528/182526.581933:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0528/182526.581971:ERROR:elf_dynamic_array_reader.h(64)] tag not found [8656:8677:0528/182527.589978:ERROR:ssl_client_socket_impl.cc(978)] handshake failed; returned -1, SSL error code 1, net_error -3 [8656:8677:0528/182527.590303:ERROR:ssl_client_socket_impl.cc(978)] handshake failed; returned -1, SSL error code 1, net_error -3 [8656:8677:0528/182527.590485:ERROR:ssl_client_socket_impl.cc(978)] handshake failed; returned -1, SSL error code 1, net_error -3 [8656:8677:0528/182527.590665:ERROR:ssl_client_socket_impl.cc(978)] handshake failed; returned -1, SSL error code 1, net_error -3 [8656:8677:0528/182527.590839:ERROR:ssl_client_socket_impl.cc(978)] handshake failed; returned -1, SSL error code 1, net_error -3 Trace/breakpoint trap (core dumped) meee@arch[~] 18:25:27 Sun May 28 $>
otoh, chromium browser itself, now v114.0.5735.45, runs fine here.
luckily i still have my turquoise-purple icon browser...
-
@ybjrepnfr
Hi, Wayland is not supported, I read you have to set some switches to start Vivaldi.
I don´t use Wayland but I hope somebody with more knowledge steps by to help.Cheers, mib
-
@mib2berlin said in Upgrade to Chromium 114 – Vivaldi Browser snapshot 3023.3:
Wayland is not supported
hi, thanks... yes, officially true, but it's been running fine in wayland here for over a year, up til but excluding this specific snappie.
i think, but might be mistaken, that in my earlier troubleshooting i excluded
wayland
as a causal-factor by logging into X11, but i might be only imagining that, so directly after this post, i'll do that test now, then edit this post... -
@ybjrepnfr @mib2berlin that was a great suggestion from you, thanks. it seems that, though i had certainly intended to, somehow during my original troubleshooting t'other day, i never got around to testing in X11, but then forgot that i'd not tested that, & stupidly then mis-remembered, ie, all this time i had been thinking i'd ruled it out. d'oh!
so what i found some minutes ago, in an X11 session, was that launching via
/opt/vivaldi-snapshot/vivaldi-snapshot - --profile-directory="NewTestProfile"
did indeed create a new clean profile & launch it. furthermore, from that profile i was able to successfully launch my normal profiles ok.i'm now back in wayland, using !=vivaldi for these posts, & after dinner shall investigate more. i already established that the chromium flag to pick x11, wayland, or auto, IS still in 114 [ie, not removed], & whilst that worked fine up til the last snappie, atm somehow it seems not to be doing its job in this snappie.
-
@ybjrepnfr @mib2berlin posting this with the snappie, in plasma wayland session, &
vivaldi://gpu
showing:XDG_CURRENT_DESKTOP ... KDE XDG_SESSION_TYPE ... wayland Ozone platform ... x11
...via
firejail --blacklist=/hdd -- /opt/vivaldi-snapshot/vivaldi-snapshot --disk-cache-dir=/tmp/vivaldi-snapshot-cache --force-device-scale-factor=1 --debug-packed-apps --disable-features=UserAgentClientHint --enable-blink-features=MiddleClickAutoscroll --enable-features=UseOzonePlatform --ozone-platform=x11
.all the following switches, which worked fine up til
3009.3
, are somehow now broken in3023.3
, & thus cause fatal crashes during launch attempts:--enable-features=UseOzonePlatform --ozone-platform=wayland --enable-features=UseOzonePlatform --ozone-platform=auto --enable-features=UseOzonePlatform --ozone-platform=default --ozone-platform-hint=wayland --ozone-platform-hint=auto --ozone-platform-hint=default --ozone-platform-hint=x11
tl;dr: on tonight's testing, the only
ozone
switch which now gives me a successful snappie launch in a kde plasma wayland session, is--enable-features=UseOzonePlatform --ozone-platform=x11
. given that's not how i've been setting my dedicated custom command launcher for snappies for a very long time, that's why all my initial launch attempts with3023.3
failed.so, whilst plasma wayland users were able to ignore [for a long time] the "official" advice that vivaldi does not support wayland, we no longer can. i wonder what internal changes caused this major UX change?
ps: anyone know, pls, if this switch is now redundant?
–disable-features=UserAgentClientHint
i suspect it has been unnecessary in vivaldi for a long time, but have not been willing to remove it without confirmation. -
@ybjrepnfr I won't disable the UA-CH at all. In the middle/long term sites which fetch mostly for it in chromium will appear. On Gecko is still experimental and is the opposite.
-
@ruarí: Огромная благодарность это работает!
-
@petyanamlt said in Upgrade to Chromium 114 – Vivaldi Browser snapshot 3023.3:
@ruarí: Огромная благодарность это работает!
Let's say you don't know what language this is. (I don't.) You select it and put it to the translator (or use "Auto-translate selected text") then you click "Translate"
Result:
Translation failed. Server could not determine the language.
Rhetorical Question: What's the point of providing a translator then, if it needs 50 words to determine the language?
-
@npro Translation, Many thanks, it works
-
Hello, thanks I got the update 3023.10 for the MacOS version but I have a question...
That's the shared changelog:
I don't see any log related the 3023.10 but it stops at 3023.3. Why that?
-
oh goody goody, now something else to troubleshoot...
-
@sev7en The suffix ".10" is for your system. All versions ending in .3 through .10 are the same release, just for different systems.
-
@ybjrepnfr afaik,
nobody
else has already posted about this... has it really not happened to anyone else for this snappie?all my menu items have vanished [for both button & horizontal menu]
both of my subsidiary profiles still have their items; this damn new problem only manifests in my
default
profile, & only since this new snappie, sigh.i see there's a settings button to
restore default menu
, which i've deliberately not yet tried ... my missing menu was heavily customised, both with custom & rearranged items, and ofc with the pretty prepended colour icons that came in a few years ago & which were all the rage in the forum back then. i presume that if i were to formally reset, all those mods would be forever lost for real, whereas atm i'm hoping they've just turned a bit shy, & someone here might know how to entice them out from their current hiding place... pls? <-- i wanted "beg", & it offered me "breast-feeding". seems fair -
@petyanamlt said in Upgrade to Chromium 114 – Vivaldi Browser snapshot 3023.3:
@npro Translation, Many thanks, it works
шумо маънои онро дорад, ки шумо метавонед инро тарҷума кунед ?
-
@sev7en said in Upgrade to Chromium 114 – Vivaldi Browser snapshot 3023.3:
I don't see any log related the 3023.10 but it stops at 3023.3. Why that?
There are no source code changes between those two builds. The only change as such is that the small build step that makes DRM work on Mac (which is not part of the Vivaldi source code) was fixed in .10, and we had actually made the same change for .3 ; but building with a new number, .10, made it possible to autoupdate the build for the snapshot users. This is the same thing we did for 6.0 Stable a few days earlier (making a .23 mac build).
-
@ybjrepnfr try to backup everything: all Vivaldi files, the whole system backup, the whole ssd image and hit that
restore default menu
-
@ybjrepnfr said in Upgrade to Chromium 114 – Vivaldi Browser snapshot 3023.3:
ps: anyone know, pls, if this switch is now redundant?
–disable-features=UserAgentClientHint
i suspect it has been unnecessary in vivaldi for a long time, but have not been willing to remove it without confirmation.According to https://niek.github.io/chrome-features/ this has changed to
--disable-blink-features=
but both when used were blocking the API part but not the header part. Both were crashing the Vivaldi Settings if you would type anything into the searchbox, so I have that "disabled" for quite some time now... Also I didn't report the latter as a bug, maybe I should have done that... , the reason for not doing that is that seriously, constantly chasing around all that neverending Chromium tracking crap got pretty old and sickening already