SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Its been a while and I am not going to download it all again, but the problem I recall was that some include directories were entirely absent from the source making it essentially impossible to build myself or for anyone to audit it.
Well last time I checked it builds for me. If it doesn't I would consider it a bug and we can rectify it.
@denydias We made a “business decision” to add this just for you. This is from an internal build (so not yet public).
In all serious, thanks for highlighting this and sorry that we overlooked it before.
This is an excellent example of the good work you are doing for the community, ruario. Just fantastic that you've decided to include that. You've really attacked this thread and knocked it into shape in the last couple of days too, great work.
Just fantastic that you've decided to include that.
To be honest it was a very simple change. Just something we overlooked mapping. Embarrassing if anything, hence the “Hanlon's razor” reference in my original reply. I hope that denydias doesn't mind my “business decision” comment. It's meant as a joke. I hope that is obvious.
[EDIT] An easy way to become aware of new snapshot releases is to subscribe to the Vivaldi Snapshots RSS feed. Or just re-run the script once a week as that is roughly how often we put out updates.
Last edited by ruario; 10-18-2019 at 08:36 AM.
Reason: Added a link to the Snapshot RSS feed
We decided to change how we handle 'proprietary' media (H.264/AAC), for the upcoming Vivaldi 2.9. I therefore made a small change to latest-vivaldi.sh. You will want version 1.6.5 of the script before you install future 2.9 versions.
P.S. Old versions of the script would still work, you just would not get working proprietary media out of the box.
We decided to change how we handle 'proprietary' media (H.264/AAC) is handled for the upcoming Vivaldi 2.9.
Do you mean that there will be an 'update-ffmpeg' script similar to the 'update-widevine' script and the proprietary libffmpeg.so will be downloaded during installation? In this case the SBo script could do the same (and we could get ride of vivaldi-codecs-ffmpeg-extra script). Would be nice!
Alternatively, in cases where they do not and support is not available, when a user first launches Vivaldi it will state the following (see attachment), with a link to the help page telling the user how to run the script.
So if the SBo maintainer prefers, they could just leave it up to the user.
P.S. Look out for a change in a future changelog with bug number VB-59143. This is when it is implemented.
@ruario I'm a little confused. Before the 2.9 release, do we need the vivaldi-codecs-ffmpeg-extra-*_SBo when using your 1.6.5 script?
From my running a grep against both packages it appears they both add a libffmpeg.so to /opt/vivaldi. So to me that means that the vivaldi-codecs SBo isn't needed with your script regardless of version. Correct?
After 2.9 release will we need the vivaldi-codecs-ffmpeg-extra-*_SBo, because it appears the proprietary video's is automatically installed by the script? Or is there a switch to turn-off loading libffmpeg?
Which libffmpeg will be install with your script?
If I've already installed AlienBob's ffmpeg-3.4.6 package why doesn't it also install libffmpeg and make that available to the browser? Am I asking a "you don't know what you don't understand and vice-versa" about raw and libraries packaging question? PS I actually see that @alienbob packages doesn't even include a libffmpeg, so the question is probably dumb, but is there an article I can read to understand the libffmpeg vs ffmpeg package differences concept?
After running Vivaldi exclusively for a bit, I'm going back to Waterfox.
I was running version 2.8.1664.44 from SBo.
Why?
(Keep in mind that I'm on older hardware which may be at least part the source of my issues.
'07 Dell Inspiron 1520, 2.8GHz C2E X9000, 4GB DDR2 800MHz RAM.)
First Vivaldi is very resource hungry. It is nice that Vavaldi doesn't hang periodically but while running Vivaldi things start dipping into swap and takes away from running other programs making them slower. It also takes at least twice as long to start as Waterfox on my system.
It seems to have a bug where if I visit a website that has a video, it takes over my volume icon in the panel and doesn't let it go until I close Vivaldi.
I cannot find any way to fine tune things like, fingerprinting, disabling geolocation (globally), etc as in Firefox/Waterfox's about:config.
Finally, some extensions don't work correctly and some not at all.
But overall, Vivaldi is a very nice browser.
Edit: One more thing, the sync needs some work. When I had it set-up on my main PC (with Vivaldi account active and synced) the way I wanted it, then I installed it on my testrig. Once I logged in on my testrig to see what gets synced, it uploaded the default bookmarks and added them back to my main rig making them a complete mess.
@ruario I'm a little confused. Before the 2.9 release, do we need the vivaldi-codecs-ffmpeg-extra-*_SBo when using your 1.6.5 script?
Yes or the browser would have told you (in terminal output only) where to find a suitable file. Now (≥2.9) it fetches it automatically on install and if that fails it tells you that it did not work in the main Vivaldi UI itself, along with a link that details how to fix it.
Quote:
Originally Posted by bamunds
From my running a grep against both packages it appears they both add a libffmpeg.so to /opt/vivaldi. So to me that means that the vivaldi-codecs SBo isn't needed with your script regardless of version. Correct?
Vivaldi only adds a file to /opt/vivaldi/lib but this file only supports open codecs. the newly bundled update-ffmpeg fetches a file (from Canonical/Ubuntu) that adds support for all media types. We do not bundle the lib with full support directly because it is patented and hence us distributing it directly is an issue. My repack script runs update-ffmpeg for you, hence why the final Slackware package that it makes already contains it.
Quote:
Originally Posted by bamunds
After 2.9 release will we need the vivaldi-codecs-ffmpeg-extra-*_SBo
I think that is up to the package maintainer to decide. There are three options
The SlackBuild fetches/configures a suitable libffmpeg for them (either on its own or by calling the bundled update-ffmpeg)
Use an extra ffmpeg package (as is the case today)
Expect the user to run update-ffmpeg (a reasonable assumption given Vivaldi itself will guide them to do this now)
Quote:
Originally Posted by bamunds
… it appears the proprietary video's is automatically installed by the script? Or is there a switch to turn-off loading libffmpeg?
You mean the new update-ffmpeg script in 2.9? You cannot turn off usage of libffmpeg in Vivaldi because it is used for all media types but you could uninstall the extra libffmpeg that adds support for proprietary media by calling update-ffmpeg --undo assuming it was update-ffmpeg that fetched and installed it.
Quote:
Originally Posted by bamunds
Which libffmpeg will be install with your script?
As stated above it is a file from Canonical/Ubuntu. They have permission to distribute this file with patented code (or at least must believe they do).
They make it for Ubuntu 16.04 and it has no dependencies outside of what you would expect on Slackware 14.2 (and above). Thus it is perfect for our usage.
Quote:
Originally Posted by bamunds
If I've already installed AlienBob's ffmpeg-3.4.6 package why doesn't it also install libffmpeg and make that available to the browser?
The libffmpeg used by Chromium browsers is heavily patched for their usage. It is not identical to that provided by the ffmpeg project upstream, so we cannot just use the normal one.
We can't even use any random one provided for some other Chromium based browser because the ABI changes over time. Pre 2.9 we were looking in a bunch of locations for suitable libffmpeg files and then testing the ones we found to see if they are suitable. This is complex and somewhat time consuming (on startup no less). So better to rely on only locations were a file is provided specifically for the specific version that Vivaldi needs.
First Vivaldi is very resource hungry. It is nice that Vavaldi doesn't hang periodically but while running Vivaldi things start dipping into swap and takes away from running other programs making them slower.
Moreso than other Chromium based browsers?
Quote:
Originally Posted by Skaendo
It also takes at least twice as long to start as Waterfox on my system.
Yes this is due to our UI being web based (which allows us certainly flexiblity and is, in part the reason for our rich feature set).
By the way, you see the same slow startup with other Chromium applications that have a web UI, like Electron apps. However once it does load It is not a massively slower UI for general usage.
Quote:
Originally Posted by Skaendo
It seems to have a bug where if I visit a website that has a video, it takes over my volume icon in the panel and doesn't let it go until I close Vivaldi.
I would again be interested to know if you see the same in other chroimium based browsers or applications as we have done nothing special here.
Quote:
Originally Posted by Skaendo
I cannot find any way to fine tune things like, fingerprinting, disabling geolocation (globally), etc as in Firefox/Waterfox's about:config.
You can disable geolocation (globally) and other such things globally in 2.9. As for more options related to limiting fingerprinting, they will likely come in the future.
Quote:
Originally Posted by Skaendo
Finally, some extensions don't work correctly and some not at all.
Some examples might help.
Quote:
Originally Posted by Skaendo
But overall, Vivaldi is a very nice browser.
Thanks
Quote:
Originally Posted by Skaendo
Edit: One more thing, the sync needs some work. When I had it set-up on my main PC (with Vivaldi account active and synced) the way I wanted it, then I installed it on my testrig. Once I logged in on my testrig to see what gets synced, it uploaded the default bookmarks and added them back to my main rig making them a complete mess.
I think I know what this issue is and it is being looked at right now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.