@ruario,

Is it possible to delete that horizontal white (history?) bar that goes across the width of the screen, without having to edit the /opt/vivaldi/resources/vivaldi/style/common.css file after every update/upgrade?

Also, it seems after every update it is necessary to re-import the passwords. Is there a way to keep the passwords from being deleted?

Thx.

1 members found this post helpful.

OK, since you are doing so - I am also going to make a request as well.

ruario - is there any way to include an option in the Settings for the taskbar window button icon to be monochrome, or for customisable Vivaldi icons [or an option for them to match the theming]?

1 members found this post helpful.

There is "Custom UI modifications" setting (to be enabled in vivaldi://experiments/). Will it do the job?

1 members found this post helpful.

Starting with vivaldi 2.9 can't play netflix videos anymore. I've upgraded to 2.9.1705.41 announced today. Still no go.

Error message says:

As vivaldi 2.9 no longer lists WidevineCdm component under vivaldi://components, I went to vivaldi://settings/webpages/ > plugins section and can verify that "Enable Widevine DRM" is enabled. Under chrome://settings > privacy and security > content > protected content (DRM) is also enabled.

So, whats up with vivaldi 2.9 and netflix? Does anybody still have the same issue?

EDIT: /opt/vivaldi/update-ffmpeg was run and proprietary media codecs (78.0.3904.70) has been installed. Nothing has changed for netflix and error persists.

https://www.linuxquestions.org/quest...ml#post6047359
Run also update-widevine. Everything should work if vivaldi installed with the latest version of ruario's script or with SBo SlackBuild, in this case there is no need manually run the update-scripts.

2 members found this post helpful.

That was quick, @salik. Thanks for pointing this post out.

I've missed that and was using an older latest-vivaldi.sh. All upgraded now, ran update-widevine, netflix working just fine. Yay!

I just wanted to say thank you to whoever it was who decided to include an option for a favicon spinner. I don't know when that crept in, but maybe I just missed it under the "tab display" options. I felt that the Progress Bar wasn't quite enough, at least with the spinner one knows that 'something is happening' on page loads!

EDIT: actually with both the spinner and the progress bar, page loading looks pretty cool.

1 members found this post helpful.

It seems the maintainer of the Vivaldi browser SlackBuild, Alexander Verbovetsky, no longer uses Vivaldi and is giving up the script for any who might want it. I don't use Vivaldi, but in case someone isn't subscribed to the SBo mailing list, here's your notification that it's up for grabs.

https://lists.slackbuilds.org/piperm...er/023505.html

3 members found this post helpful.

I guess if nobody takes it I will take it myself

4 members found this post helpful.

I would in theory, but I know little about maintainership and don't have time to learn at the moment. I would say you're the best man for the job, ruario. However, you can count on me as a 'second' should you ever feel like you want to pass it on in the future.

1 members found this post helpful.

Within the past year I have been increasingly favoring Vivaldi over Firefox. Firefox, to me, has been looking and feeling bloated since the new Quantum engine and less customizable.

As with Firefox I found that a SlackBuild is not necessary unless you need some of the extras such as icons or menu entries. I just grab the latest deb or rpm from Vivaldi's site and extract the vivaldi directory to /opt (or wherever I want it). Works fine. And as mentioned recently, the first time I launched a 2.9 version I noticed on the home page a message about the plugins not being installed and to run update-ffmpeg. When I went to /opt/Vivaldi to run it I found and ran update-widevine at the same time.

3 members found this post helpful.

Building it from the SlackBuild just adds the use of the pkgtools, ie; upgradepkg, installpkg, and so on. While it might not be "necessary" it does add an additional layer of ease. Keeping the Slackware-style .tgz/.txz you can reinstall and upgrade (for some users) easier.

But if manually installing it is how you are more comfortable, by all means do it! With Vivaldi (and similar repackage SlackBuilds) there is no need to recompile so it works either way.

I am aware I am posting in slackers forum.

Its my wish that for Vivaldi to be a "friend of the internet" it offer the same function of FF which allows FF to run from your home dir and get only diff files for point releases.....saving the internet bigger downloads.

Yes I am aware that FF is one of the bigger web browsers out there.

If @ruario is interested, here is my evidence.

ref https://support.mozilla.org/en-US/kb...-firefox-linux
comments
########

As you can see.....its almost a "Portable" package like a snap or appimage....but IMHO not a complicated as those....because you do not need snap or appimage installed to use FF from unpack.

Because FF has frequent updates......I do not break the internet because my point releases tend to be only a couple of megs because most files do not need updating....but a major release (integer release) is a full download

If ruario or the Vivaldi dev team can see big picture reasons why they won't do this, or like it
feel free to say so.
PS I just looked at Vivaldi on my Android and they seem to welcome feedback!

but I have 82 items with an unpack size of 200 Mb....yep FF is big.

EDIT just installed deb of Vivaldi its 216 Megs of unpack...hmmm

1 members found this post helpful.

@aus9 Thanks, I am aware of the tar.bz2 packages, since I use them as a source for my latest-firefox script that several people on the Slackware forum use.

FWIW, You don't need a tar for this. You can just as easily unpack any of the Chromium based browsers already and run them in place. You will notice that in my recent request for help in diagnosing a Chromium 79 issue, I provided steps to do just that with Chrome, Opera and Vivaldi.

This works because none of the Chromium browsers require any major dependencies outside of what you would expect to find on a typical Linux distro setup for desktop usage. In case you were not aware a .deb is just a couple of compressed tar archives (and a text file) wrapped up in ar archive container, while an rpm is just a compressed cpio archive with some meta data tacked on the front. Either package is trivial to open (extract from) on a modern Linux system. You don't even need any special tools. You can extract from either with little more than tar/cpio and the relevant decompressor (xz). Just grab either one, unpack it in home or wherever you feel is suitable and run the executable. Done. Sure, I guess it is nice that Mozilla provides a straight compressed tar for those that do not realise that deb and rpms are essentially the same thing but I am not convinced that they do this for the user benefit. More likely they do not want to deal with packaging up rpms/debs and prefer to leave that to the community, which I get. Providing single rpm/debs that are generic enough to work on a wide range of distros, while trying to stay within normal packaging conventions of each distro is hard.

You also do not need a tar to implement delta upgrades. The browser could check if it has write permission to its install directory and if so it could self update. This is a different request to providing a straight tar and something we could look at. Other ways of handling this could be Snap, Appimages, Flatpak etc. each of which support delta updates.

That said, whilst the delta support they provide is nice their tar is not ideal IMHO. They choose to package it bz2 compressed which means it is 14Mb larger than than a similar archive using XZ compression. Why are they wasting 14MB of download data for every single user who downloads it? FWIW, Vivaldi, Chrome, Opera, Brave, etc. use XZ compression in all their officially provided packages.

1 members found this post helpful.

@aus9 Here is an example

OK, yes I precalculated the offset positions of the compressed tar within the deb (ar archive) in case you don't have ‘ar’ (from GNU Binutils) on your machine.

If you feel that is cheating here is an alternative:

P.S. For anyone curious about how I worked out the offsets. It does not require any special, inside knowledge from Vivaldi. I just inspected the deb files with ‘ar’ and ‘grep’.

The following will show you what files are inside the ‘ar’ archive, along with their order and length

Note that ‘data.tar.xz’ (which are the installable files) is the second XZ compressed archive and it is 63691192 bytes long.

Now we can use grep to search for and print out the position(s) where the XZ magic numbers (0xFD, '7', 'z', 'X', 'Z'…) appear.

Since we already know the second entry is data.tar.xz, we now also know its starting offset is 9720.

1 members found this post helpful.