** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** No longer affects: nss (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All
Thanks, Dino !!!
I've been fighting this battle for a few days under Chromium 45 (same as
other's problems above - and more).
Upgrading to "47.0.2526.73 (Developer Build) Ubuntu 16.04 (32-bit)"
restored my Chromium install to sanity.
Everything appears to work normally now.
--
You received
Confirm that version 47 works here too , even if the issue described above
(#29) is still not resolved.
Chad as been asked to upgrade to version 47 ( Bug #1522411 ) , so its a
matter of a couple days to get it into xenial archive.
** Changed in: nss (Ubuntu)
Status: Confirmed =>
The PPA Chromium 47 also fixed it for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR
To manage
I've tried a newer version of chromium-browser (47) from this ppa:
ppa:canonical-chromium-builds/stage
And it seem to work normally.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
I tried libnss just now with version 3.21 and it fails consistently. I have
downgraded again to 3.19 to keep work going on...
To me, if it's not libnss itself, then it's some weird interaction with the
last version of it.
--
You received this bug notification because you are a member of
Chromium settings:
chrome://settings (with libnss3 3.21-1ubuntu2)
-> HTTPS/SSL , Manage certificates :
- your certificates : empty list
- servers: Global Trustee -> untrusted; Google Ltd -> all untrusted
So if the latest libnss3 version is not faulty, then its a chromium
#29 addon
as a side effect with chromium, the auto translate feature also has
stopped working
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All queries fails when
just to get notified
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR
To manage notifications about this
This bug also affects https://te-st.ru
Can somebody reproduce?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All queries fails when 'google' is used:
I can't reproduce this issue in midori at all.
I can reproduce it with https://te-st.ru
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All queries fails when 'google'
Midori feedback:
my problem was due to something else: after purging then reinstalling
it, the problem is gone. Sorry for the noise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
@Bryan
Get the same issue with midori (its confusing as it is not directly depending
on libnss3).
The default browser used is 'google'; and i get that issue when:
- i use the 'google' search field
- i type an incomplete part url into the top url bar (without http://www.)
So the steps are
Doesn't affect duckduckgo.com etc but only google (sub)domains!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All queries fails when 'google' is used:
@dino99 I can't reproduce this with midori. Are the symptoms identical
for you? Are there any midori specific steps?
I couldn't reproduce this issue on Debian sid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
> dino99 (9d9)
> Looks like related to these changes:
> nss (2:3.21-1)
The question is, why the Google Chrome is not affected by this, since it
depends on the same library?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in
nss 3.20.1 works, nss 3.21 doesn't.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR
To manage
confirm #19 test above
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR
To manage notifications about this
On Dec 01, 2015, at 01:38 PM, Marc Deslauriers wrote:
>1- I can't reproduce this by installing the daily live cd in a VM
>2- I can reproduce it successfully by installing the daily live cd on real
>hardware
Confirmed that my working machine is a VM and the busted one is physical
hardware.
--
@Igor
- chromium is affected, and indeed use the faulty libnss3 package (which works
again if libnss3 is downgraded)
- midori is also affected, but does not use libnss3 as a dependency directly;
supposing some sub-depency is disturbed
- problem exist with 'google' as the default browser, but
OK, a few more notes on reproducing this:
1- I can't reproduce this by installing the daily live cd in a VM
2- I can reproduce it successfully by installing the daily live cd on real
hardware
This means it's probably not related to which Google servers are being
hit, and is likely
On Nov 30, 2015, at 08:51 PM, Bryan Quigley wrote:
>@barry.. Maybe do LiveCD tests on both of them to see if it's a
>configuration issue or if it might be hardware related.
I'd be very surprised if it was hardware, but I can try it. I never had this
problem on this machine until this morning's
Thank you bq.
Hrm, it's error -12218 SSL_ERROR_ENCRYPTION_FAILURE
"Bulk data encryption algorithm failed in selected cipher suite."
** Changed in: nss (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
I just tested with the latest image (via testdrive). All I'm doing is, adding
universe, installing chromium.
On open the second tab fails to load (guessing it's login to Google), trying
google.com or blogger.com also fails.
I can also reproduce in canonistack, Marc and Chad I added your ssh
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
I just noticed this today. AFAICT, it only affects https to
www.google.com and other Google subdomains (first noticed on
docs.google.com). It does not affect Firefox.
Odder still, I have two fully up-to-date (AFAICT) Xenial machines, both
amd64. One of them connects to https://www.google.com
@barry.. Maybe do LiveCD tests on both of them to see if it's a
configuration issue or if it might be hardware related.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
Same error here, and the package downgrade fixes it for now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All queries fails when 'google' is used:
Which IPs show the errors? It could be that different results may be due
to different TLS terminators at Google. Figuring out one specific IP
that demonstrates the issue may help (assuming Google hasn't done
something crazy like anycast on their search IPs).
--
You received this bug notification
Looks like related to these changes:
nss (2:3.21-1) unstable; urgency=medium
* New upstream release.
* nss/lib/ssl/sslsock.c: Disable transitional scheme for SSL renegotiation.
5 years after the transition started, it shouldn't be necessary anymore.
*
I can't seem to reproduce this. https://www.google.com works fine in an
up-to-date image with Chromium and nss 2:3.21-1ubuntu2.
Could you please give the exact steps require to see this issue?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: nss (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568
Title:
All queries fails when 'google' is used:
32 matches
Mail list logo
