the logs?
start a new thread and detail steps that lead to the freeze.
"the logs" and anything else you feel is relevant

A minor update to Vivaldi 2.8:
https://vivaldi.com/sv/blog/minor-up...r-vivaldi-2-8/
Seems to work for me. I haven't had any issues with Vivaldi 2.7.x or 2.8.x.

Edit:
Yet another minor update (2.8.1664.40)
https://vivaldi.com/sv/blog/minor-up...r-vivaldi-2-8/

3 members found this post helpful.

Fourth minor update for Vivaldi 2.8 is available:
https://vivaldi.com/sv/blog/minor-up...r-vivaldi-2-8/

3 members found this post helpful.

Opera fired the entire core team in Oslo who were the main people maintaining the Presto rendering engine. This was followed by several more rounds of firing (primarily in Oslo) over the coming years. By the time I left there were almost no engineering left in Oslo. Now as far as I know there is none. Opera is Norwegian in name only and is owned from Chine and primarily developed in Poland with small teams in places in one or two other countries. I think there are a few people left in Sweden and fewer still in France.

Here is a link from the Brave blog with regards to phoning home https://brave.com/brave-tops-browser...affic-results/

Also if you are interested in tracking and privacy you might also want to read this https://vivaldi.com/blog/how-we-count-our-users/

We have had a bug where the preferences don't reflect that Vivaldi is the default but you can check if it set itself corrected via a test like `xdg-open http://elg.no`

This is very actively being worked on. There are a few bugs in the last stable. I hope we are in a better shape for 2.9

1 members found this post helpful.

With Chromium 28 (which powers Vivaldi 2.9) there have been some changes in where Widevine is installed. I recently updated the script I wrote for Vivaldi that fetches and installs it and have had to adjust the latest-vivaldi.sh accordingly. If you don't have latest-Vivaldi.sh Version 1.6.4 or higher, fetch it now.

P.S. The script supports installing snapshot versions alongside stable with if you launch it as follows:

I released the a new snapshot today Address bar and menu improvements – Vivaldi Browser snapshot 1697.4

2 members found this post helpful.

@BroX Regrading Tidal, if you ever have a problem with it, let me know. I know the QA lead for the web based product. He is my ex-manager from Opera (and Vivaldi initially) and the brother of Jon von Tetzchner (Opera and Vivaldi founder). He is also someone I regularly meet up with for lunch. If you follow the snapshot blog posts and see a guy saying “First!” called Olli. That is him.

Oh and he also likes to spend his time trolling me on twitter, for example: https://twitter.com/olafura/status/1175109863938121729

1 members found this post helpful.

My latest-vivaldi script calls another script I wrote that is bundled with vivaldi called update-widevine. This is almost certainly what fixed the situation for you. Incidentally if someone is using the SBo version of the package they can call the script manually after install as mentioned previously in this thread

The SBo script installs widevine, hence no need to do anything. Am I wrong?

1 members found this post helpful.

Ah yes it does, I see that now. Sorry, I had not looked at it for a while. It'll need a small tweak when 2.9 comes out but no problem as we aren't there yet.

1 members found this post helpful.

Ok, I realised I missed a few replies. So I have gone back again. If I missed something else. Sorry just reply here again to remind me and I will do my best not to forget you again!

Because maintaining a decent rendering engine in the modern world requires an engineering team of hundreds. That is what we had at Opera before we killed Presto and Presto was simple compared to Webkit/Blink or Gecko/Quantum.

The entire Vivaldi company is 40 people. Of that 15 are listed of devs but more than half of those are working on Android, projects like Mail and Calendar or services related to our website. The entire Vivaldi desktop UI is created and maintained by maybe 7 devs. We are a long way off being able maintain a fork of one of these rendering engines and starting one from scratch is another thing entirely. You will have noted that not only Opera has dropped their engine development but even the likes of Microsoft.

Actually, yes you could. The UI is written in HTML/JS/CSS and can be inspected with dev tools just like any website. The code changes we make to Chromium to allow our UI to run are open source and uploaded here https://vivaldi.com/source/

Not really, because we don't exculsively care about Gtk. We also expect to run in environments that are Qt based or the toolkits of the other OSes we support. Our UI is not Gtk based, it is based on web technologies (which is one of the reasons it is so flexible). However it does mean that handling Gtk themes is non trivial. That said we have quite a wealth of UI and themeing customisation options, so you could probably approximate your Gtk theme with a little effort.

True. I cannot dispute this.

“some crucial files missing”. Do you care to explain why you believe this?

The only thing that is missing is our HTML/JS/CSS UI. Try compiling it (it is possible, there are some basic instructions included, albeit for Ubuntu). You will end up with a functional browser. It won't look like Vivaldi because our UI is not included in this bundle but you can lift the HTML/JS/CSS (which are all text based and inspectable) from one of the binary packages and you will have a working Vivaldi.

You are the one making a claim but not backing that up. What are you basing that on? As I said, try compiling it and you will find otherwise.

Do you see the same with Chromium? Because we have made no changes to this area of the code and I have seen some people complain about the same thing with Chrome. Most likely this is a Chromium bug that some people hit and others (the majority) do not.

Please nobody do this, it causes Chromium browsers to store passwords in plain text on disk.

That is super kind, thank you. And applogies for not reviewing this thread more often, with other projects we have been working on (e.g. Andriod) and things going on in my personal life (nothing bad), I have been quite distracted from the Slackware world for some time.

We do try our best to accomodate users rather than taking a we know better than you approach as so many software companies do these days. We also appreciate that everyone has a different workflow. Hence all the options, rather than trying to force everyone to work the same way. One of the companies that does this the most being Apple, which is funny, given their “Think Different” slogan.

The first response is from Gwen-Dragon, who is a volunteer with special access to devs and internal resources. Her comment is correct, you can use Chromium settings to globally disable them via “chrome://settings/content/notifications”. I have tested myself and it appears to work.

The issue is a lack of UI for this. However it is not a regression, by that I mean something we had that went away. We have just never mapped our settings to this and outside of this thread I cannot find any feature request in our bug tracker from any user requesting this. So the short version is I was not aware this was a request and since Gwen had replied to that thread I doubt any employee spent time looking at it. That said, if you want it in our settings, sure. I have just logged it myself as VB-58931. I'll ping a dev or two and see if I can get one to hook it up.

Hanlon's razor, “Never attribute to malice that which is adequately explained by stupidity.”

Also what would that business decision be? I can't see that there is any financial advantage to us not to implement this. Here is our business model

https://vivaldi.com/blog/vivaldi-business-model/

Could you provide an extact URL you are testing against that demonstrates the problem? This would allow others to verify.

I would also suggest you try with a clean(test) profile/settings, make the one change in Chrome settings and see if this resolves it. If it does it is some other setting or extension overriding your changes. You can start with clean settings like so:

Ah great! Indeed you cannot change settings from a private window. Nonetheless, I shall leave my previous comment in as it may help someone with testing in the future.

I have heard other users report it. We have not reproduced thus far but are still investigating.

6 members found this post helpful.

(emphasis mine)

Just had a thought with regards to why you might be confused. We use the Chromium networking code, we do not have our own.

Earlier you mentioned:

You realise that the “7.3 GB of chromium source” is not identical to vanilla Chromium source, we have made changes there as well. It is patched, which is why we include it in our source bundle. If it was pure Chromium, we would not bother and just provide a link.

1 members found this post helpful.

Re. using --password-store=basic:
It does, which is risky, but only if you allow your browser to store passwords.
Never a problem for me with vivaldi, but with chromium I always got those irritating pop-ups demanding a pw and I thus opted for the basic pw store alternative without actually storing passwords. Great memory training, too

I suppose I should clarify. Do if it you like, for your reason or any other that suits you. It's your computer and your passwords after all.

But when advising people of this option make sure they understand that if you do choose to save passwords with this switch enabled they will be in plain text on disk. That is the main issue I have with the suggested fix/workaround, i.e. that most people suggesting it as a fix do not point out what it actually means by ‘basic’. IMHO this password store should have been called ‘unencrypted’.

4 members found this post helpful.

I'll second that.

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.