Upgrade to Chromium 114 – Vivaldi Browser snapshot 3023.3
-
@jimtdi: Whatever that issue is, it has zero to do with the libffmpeg, I am certain of that.
You are starting to have these problems after the restart but it is not related to installing the file.
-
@Ruarí I am certain it's not that file also. I did not restart the snappie because it wasn't running so I just started it after following your instructions. I will try again with a clean profile. Thank you for your time and have a nice weekend!
-
@Ruarí - with a clean profile, and copying the libffmpeg file it now worked. Thank you again!
-
@jimtdi: Glad to hear it though concerned about the other bug but I think I will worry more about it next week. Have a nice weekend!
-
For some reason, for me, all the text in every menu has become really tiny as of this snapshot. No text anywhere else in the GUI is affected, though...
EDIT: I stand corrected! It's also affecting confirmation dialogue boxes, such as "Confirm Window Close", or "Confirm Form Resubmission".
-
This snapshot broke my install. Buttons missing, pages render out of whack, on this machine.
HP Resolve 810 with Mint Mate - I7 on-board graphics.Complete removal, reinstall snapshot 6.1.300~ and working again.
Get update notice to 3.1.3023... broken again with error so definitely this update.Restore snapshot ot 3.1.300~ and get error:
Mail client startup failed. ... requested version (1980) is less that the existing version (1990). VersionError: etc etc...Here ya go.
and
-
@Ruarí nice one, thanks. works fine for snappie in my fedora 38 kde laptop.
didn't bother running these commands in my arch tower though, coz as per earlier posts, latest snappie does not launch there.
edited:
following successful discoveries per https://forum.vivaldi.net/post/670634, i have now applied your commands also in my arch kde pc, & ofc they also worked fine there as well. thanks again. -
@xr3y6rs
Hi, there was a jump from Chromium 112 to 114, I guess GPU/driver/Vivaldi issue.
You can try to start Vivaldi without hardware acceleration in a terminal:
vivaldi.snapshot --disable-gpu
Or disable it in the Settings > Webpages, restart Vivaldi.
What do you meant with "restore", lower Vivaldi version with newer profile?Cheers, mib
-
@mib2berlin said in Upgrade to Chromium 114 – Vivaldi Browser snapshot 3023.3:
What do you meant with "restore", lower Vivaldi version with newer profile?
Figured something in regards to Chromium version.
On Mint Mate... I used timeshift to restore to an earlier version (3009.3) which worked fine, and where I am now, with no mail, but I have other machines.
*editvivaldi-snapshot --disable-gpu
Works. Didn't at first. Had two instances running.
Workaround: edit launcher properties command in panel to/usr/bin/vivaldi-snapshot %U --disable-gpu
kludgy but mail works again
-
As before...
Still crashes upon wake from sleep!
-
@OakdaleFTL
Hi, I am not sure I ask this before, which sleep mode did you use?
In German it called Stand-By and Ruhezustand (Hibernate), Hibernate save the session to the disk, Stand-By to Ram.
I use Stand-By all day on my laptop, Vivaldi never crash for me.Cheers, mib
-
@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.