Comment 4 for bug 1547762

[b]Concerning this Bug,[/b] the ERR_SSL_PROTOCOL_ERROR issue specifically affects Alphabet Corporation properties (viz., Google® Search℠, Google+®, Google® Hangouts℠, YouTube℠); I had little trouble logging into SingSnap® from chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917. My own Ubuntu® 12.04.5-LTS rig as updated with packages related to Kernel 3.13.0-generic has the following Release and APT Cache data concerning chromium-browser:
[code]$ lsb-release -a
Distributor ID: Ubuntu
Description: Ubuntu 12.04.5 LTS
Release: 12.04
Codename: precise
$ uname -a
Linux hotrodgpc-desktop 3.13.0-78-generic #122~precise1-Ubuntu SMP Tue Feb 2 21:27:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ apt-cache policy chromium-browser
chromium-browser:
  Installed: 37.0.2062.120-0ubuntu0.12.04.1~pkg917
  Candidate: 37.0.2062.120-0ubuntu0.12.04.1~pkg917
  Version table:
 *** 37.0.2062.120-0ubuntu0.12.04.1~pkg917 0
        500 http://mirrors.us.kernel.org/ubuntu/ precise-updates/universe amd64 Packages
        500 http://mirrors.us.kernel.org/ubuntu/ precise-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     18.0.1025.151~r130497-0ubuntu1 0
        500 http://mirrors.us.kernel.org/ubuntu/ precise/universe amd64 Packages
[/code]
Incidentally, has a Bug been opened for libnss3 and/or libnss3-1d, which appear directly related to the ERR_SSL_PROTOCOL_ERROR issue?