Webkit fails to login to Gmail

[Ceridwen]

I noticed this first in Evolution, when I tried to log into a Gmail account through its API.

1. The page containing the first Gmail prompt, for the username/email addresses, would take several minutes to load.

2. When it did load, after entering the username/email address and hitting next to move forward to the password prompt, it would again pause for several minutes and then fail (probably time-out) with the message from Google, "Something went wrong. Check your connection and try again."

This also happens when I try to login to Google through gnome-control-center and "Online Accounts" and through Epiphany.

I've been having intermittent failures due to IPv6 on 16.10, being unable to reach some sites because DNS would resolve them to IPv6 addresses, including Google. However, I tried disabling IPv6 through Wired Settings and this didn't change the behavior.

I only noticed this in the current version of Webkit2 because when Evolution changed to 3.22 from 3.18, when I switched from 16.04 to 16.10, it started using Webkit2 for Oauth authentication to Gmail. It may exist in earlier versions too.

While I was debugging this, webkit2gtk-4.0_WebKitWebProcess segfaulted, and I used Apport to send the information on that crash.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libwebkit2gtk-4.0-37 2.14.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Thu Jan 19 15:10:27 2017
InstallationDate: Installed on 2017-01-12 (6 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: webkit2gtk
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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