Something must be wrong with your Vivaldi setup, or Google have different unwritten rules for their US users. I have a Vivaldi tab signed in permanently to Gmail. The web interface, by the way, not the Vivaldi mail client.

I've never had issues signing into gmail.com (sync is turned off). Do you mean the Vivaldi email client? There's a setting for "less secure apps" in Google's "Account > Security." At least as of a few months ago, that was working for me.

The catch is that the setting is unavailable if two-factor authentication is turned on. In that case, an "app password" (again from Account > Security) can be generated for Vivaldi and used to connect a gmail account to the client. No hitches here so far.

Had the same experience a week or two ago, found a solution:

Go to vivaldi://settings/privacy/
Make sure to check the "Crypto Token" box under the heading "Google Extensions".

I seldom fiddle with my google account google services via browser (reading my gmail in Thunderbird), so not sure when this was added to Vivaldi.

2 members found this post helpful.

Many thanks!
It says right right there, "You will be unable to log in to Google services with this option disabled," but I never noticed.
I also use Thunderbird, but once a week or so, go directly to google's mail server to check for
spam and clean out the trash.
Thanks, again.

Vivaldi 5.0 has been released.
https://vivaldi.com/blog/vivaldi-5-0...wd=subscribers

1 members found this post helpful.

Are there any resources about configuring vivaldi in batch mode, via shell script?

I'd like to do the following:

- install the Markdown Preview Plus extension
- in its details, toggle the "Allow access to file URLs" switch to on
- it its options, toggle the "Enable auto-reload" checkbox to yes

I would like to do this in a scenario not involving the X server, by copying/modifying files only instead of trying to automate the GUI to click on stuff.

Is this possible at all and how to approach it?

What's the latest Vivaldi running on stock 14.2 on your side?

mine: 4.3.2439.71 (Stable channel) stable (64-bit)

For those in need of an fully functional vivaldi browser on the (hopefully) soon to be deprecated 14.2 Slackware:

Will generate a package in /tmp/

(the latest-vivaldi.sh seems to be shipping with your current vivaldi package (if you are upgrading) so just
and if lucky at all it should surface somewhere within /usr/doc/*, if totally out of luck find it here, somewhere on the forum)

NOTE: This is in no way recommended nor most secure option - just a dirty hack until 15.0 alleviates the issues of long old glibc versus modern and recent binary-only release.

The most recent build, however working (and quite slick at that matter) is failing to perform a task (or two) for me, so i post this here in case other members might benefit of this procedure as well.

1 members found this post helpful.

Does anyone knows how to change the background of the "profile chooser" ? All this white is so ugly with my dark theme ! I would have imagine the theme background would be used here.

I've used latest.sh to ugprade to 5.1 of vivaldi for a 14.2 stable version. DRM is no longer playing. DRM played in vivaldi 4.3, did not in 5.0, and doesn't not in 5.1. Is this a libraries too old issue? Will the old 4.3 vivaldi branch continue to get security updates? Thanks

It seems there are quite a few things I need to address in this thread but now is not a great time for me. However, I will comment on yours @bamunds because I can give a very quick answer. It is not lack of DRM it is lack of support for proprietary media because the glibc version in 14.2 is too old for the third party chromium patched libffmpeg that we fetch. 15.0 users would be fine.

You can work around it with this https://gist.github.com/ruario/d3d4b...20ea24308abfc0 for the time being.

And no Vivaldi 4.3 is not supported and should not be run. The Chromium version is too old. There are known zero day exploits in older Chromium.

3 members found this post helpful.

Thanks for the quick answers. Appreciate the quick support. I'm waiting for 15.0 to settle, especially since the platform I run slackware on is 10 years old new hardware support isn't a driver. Plus I'm a little old school with FVWM3, but often get the dreaded "Your browser is not supported" message and reference to try Chrome. This should do the trick.

Edit: ran the script and it built the libffmpeg.so.5.1. In slackware it was then a simple matter of cp the file to the /opt/vivaldi location. Everything now seems to be good. Thanks ruario!

1 members found this post helpful.

Vivaldi is rated as one of the top three most secure browsers in this article,
https://linuxiac.com/most-secure-linux-web-browsers/

"Brave takes the spring out of creepy bounce tracking"
https://www.theregister.com/2022/03/...unce_tracking/

I see that Slackbuilds is still not accepting submissions. FWIW, this is the SlackBuild I would have attempted to submit for 5.1.2567.66.

https://downloads.vivaldi.com/stable...build-2.tar.gz

Alternatively, you can just get a package directly from here that I built for my own usage:

https://downloads.vivaldi.com/stable...64-1ruario.txz

[The main difference between them (besides the latter being pre-built) is that I kept the package naming for the SBo version as it was, prior to my taking over maintainership, i.e. the package is called "vivaldi", rather than "vivaldi-stable". That simplifies upgrades for those already using a SBo package. Although one could always do the % trick anyway, `upgradepkg vivaldi%vivaldi-stable-5.1.2567.57-x86_64-1ruario.txz`.]

A further comment, since Slackware 15.0 is now the most recent stable version, the packages are somewhat "optimised" for that. What does that mean? Well in the official rpm and deb packages (that I also happen to be the primary maintainer for) we fetch a third party (Chromium-patched) libffmpeg in post install, since we do not have rights to ship it directly, due to patents for H.264/AAC support. I decided to do the same now here on Slackware as well. I had avoided it previously because it would have left a single (untracked by pkgtools) 3.2M file hanging around (in /var/opt/vivaldi), should the user uninstall. With Slackware 15.0, support for the new douninst.sh was added to pkgtools. So I can now use this to remove that file on post uninstall and keep everything nice and clean.

If you do still use 14.2 however, be aware that you will probably want to remove this file manually (if you ever decide to uninstall Vivaldi). If you never remove vivaldi (which obviously I would hope) then upgrades will be handled, even on 14.2. By that I mean the file will get replaced with new, more suitable ones with each update. Or to put it another way, you will not end up with endless copies of this file. It will only ever be the one. Still, it is probably worth being aware of.

6 members found this post helpful.