Constant and frequent SSL handshake errors in logs

[Mike Holownych]

I am seeing constant and frequest SSL errors in the logs from gnome-shell:

cloudbox gnome-shell[13711]: [13757:13763:0827/085507.253897:ERROR:ssl_client_socket_impl.cc(981)] handshake failed; returned -1, SSL error code 1, net_error -202

mike@cloudbox:/opt/qbittorrentvpn/qBittorrent/config$ sudo lsb_release -rd
Description: Ubuntu 20.04.3 LTS
Release: 20.04

mike@cloudbox:/opt/qbittorrentvpn/qBittorrent/config$ sudo apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.36.9-0ubuntu0.20.04.2
  Candidate: 3.36.9-0ubuntu0.20.04.2
  Version table:
 *** 3.36.9-0ubuntu0.20.04.2 500
        500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     3.36.4-1ubuntu1~20.04.2 500
        500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages
     3.36.1-5ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Aug 27 08:52:33 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2021-08-06 (20 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

That's Google Chrome/Chromium. It just fails to identify itself correctly in the log so still has the name of the process that launched it.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.