ubuntu16.04 vivaldi install fails to load https:// sites
-
I am somewhat newbie. Using 18.1MintCinnamon (ubunt16.04)
I loaded Vivaldi from the current Deb . Program booted fine but it does not allow any web pages to load that are https:// I only know of one site that is old http:// and it loads fine. When a URL points to any website with commonplace https:// echoed into the address bar then the bar turns reddish and a small "i" appears on the left end which is clickable.
It opens a dialog stating "your connection is not secure" and links are offered to "site settings" . I toggled all the settings to "allow" and it makes no difference to behavior. I found equally that Chrome version 73.0 installed from a deb in 2019 has the same failure to load https:// sites. I downloaded and installed Chrome ver 83 current and it does the same
First: is there anyone reading this list who has Mint 18.$ installed who has successfully installed current Chrome or Vivaldi with no problem?
In each case I have installed with "debi" package manager. It is interesting that I can view the addition of each of the CHrome installs in the synaptic database of software ....but the Vivaldi install from Debi does not show up (I guess because NO version of Vivaldi haas been in the repository at ubuntu)
Second: Some how I think this is some common library item in 18.$ that is affecting both vivaldi and Chrome?
Third: How could this behavior in both chromium based browsers be caused by "configuration" in each program? What and where is the dependency library that each program is expecting but not receiving in the 16.04 deb or the base linux distribution?
this is over my head Thanks in advance
TMay
I -
@tmay said in ubuntu16.04 vivaldi install fails to load https:// sites:
is there anyone reading this list who has Mint 18.$ installed who has successfully installed current Chrome or Vivaldi with no problem?
I am using Mint 18.3 and have no problems installing Vivaldi (both Stable and Snapshot).
Note: I've successfully installed each Vivaldi version update since I was using Mint 17.x (back when Vivaldi was "tech preview").
Which version of Vivaldi are you using/trying?P.S. I have not installed Chrome or Chromium, however I do also have Opera (also Chromium based) installed and working.
In each case I have installed with "debi" package manager. It is interesting that I can view the addition of each of the CHrome installs in the synaptic database of software ....but the Vivaldi install from Debi does not show up (I guess because NO version of Vivaldi haas been in the repository at ubuntu)
I installed the "deb" package(s) - is that the same as your "debi"?
Maybe this article will help you:
https://help.vivaldi.com/article/manual-setup-vivaldi-linux-repositories/You may also find this one useful
https://help.vivaldi.com/article/html5-proprietary-media-on-linux/Nor do I have problems loading https:// sites!? No configuration needed, just runs after install (although I have modified quite a few settings from default over the years).
Also, this Vivaldi forum is https:// does it also fail in Vivaldi for you?Finally, you don't mention if you have any extensions installed?
-
This problem was solved by extensive apt-get update of the Mint 18.1 installation followed by two passes of
apt list --upgradeable and sudo apt-get upgrade
The update to a long time for a system that had never been consistently updated . ' I dont know which dependency lib file was the critical dependency. I am guessing that installing a package that is outside of ubuntu repositories may not give the info needed by apt to check for some dependencies. By bringing my whole system uptodate I guess the right lib file got in there.. A part of the upgrade log included settingup and removing various certificates accumulated over time and I dont know if that affected the refusal to load https:// sites
Using uptodate firefox on this older MInt had no problems
Trying both vivaldi and chrome they shared the behavior that going into the SiteSettings menu > Certificate Management , one click on that menu item would instantly crash the program. So it may have been a problem with handling certificates ,,,but the immediate crash suggests a defective library dependency
Tmay -