"Your connection is not private" on google sites

Ayespy

@astral: What that tells you is that Google does not comply with the security requirements of their own new engine. They will either have to modify Chromium 56, or their own websites, before 56 is officially released to the public.

astral

@Ayespy But why doesn't this affect other Vivaldi users ?

Ayespy

@astral - Dunno. Have you tried the 32-bit version that most people use?

astral

@Ayespy I have installed the 32-bit version and nothing changed.

Ayespy

@astral - Hmmmm. I'm stumped. Do you use any privacy or security extensions?

astral

@Ayespy As I wrote in previous posts, I have only 3 extensions that even if I disable them I still get the same message.

astral

Ok, I have reverted back to 1.7.721.3 (Official Build) dev (64-bit) and everything is working as it should.

So I guess it's chromium 56 that is causing this.

Also in the latest snapshot I could not play music from bandcamp, but is working without a problem in 1.7.721.3.

Is there anything I can do to follow the latest Vivaldi snapshot releases, or I'm stuck with this version maybe until a new chromium version?

Ayespy

@astral: both Vivaldi and The Chromium Project will be working on fixing this.

astral

Just stating that the problem persists in the latest snapshot, regardles the chromium update to 56.0.2924.68.

Hence, I'm staying with snapshot 1.7.721.3 for the time.

raybert

FWIW, OP is not the only user with this problem. I started getting this issue today after updating from 1.6 (stable) to 1.7 (stable -- 735?). I'm running an old fedora (17) but all other browsers were working including vivaldi 1.6. I tried everything in this thread and nothing worked. I downgraded to the 1.7.721.3 snapshot (like OP) and now works. The problem certainly looks like chromium 56.

BTW, somewhat unrelated but is it safe to allow stable & snapshot to share a config dir (so I don't have to manually re-config when switching)? I just tried mv vivaldi-stable vivaldi-stable-backup; cp -r vivaldi vivaldi-stable and that seems to be working but would symlinking the dirs be safe?

Thanks!

raybert

ok thx. That's what I expected but thought I'd ask anyway. fwiw, I would never run stable and snapshot at the same time. I try to stick with stable unless I run into a problem (and I'm happy to say I think this is the first time -- so nice job guys!

btw, I just noticed I accidentally wrote "-stable" when I meant "-snapshot", but I guess you understood what I meant anyway.

thk again!

astral

Ok the problem was resolved for me when I performed all Level 3 updates on Linux Mint.

The reason I did not make any Level 3 updates until now was because of their description: " Not tested but believed to be safe".

I'm not sure which one did the job though.

grinzold

Updating libnss3.so fixed this issue for me on a really broken old Debian installation.

AR