Not able to log in into Google Account, aswell as Microsoft account

[Matheus Reich]

After the first boot up of Ubuntu 18.10, it invites me to log-in into several accounts, including Google and Microsoft accounts. After I log-in into Ubuntu One, my next step is to log in my Google Account, but the log-in page never loads, and when it does (after a couple of minutes), and I insert my log in credentials, it fails the log-in process, all of this happens with the Microsoft account too. The Ubuntu One account logs-in without a hitch, but the rest does not.

1) Description: Ubuntu 18.10
Release: 18.10

2) gnome-initial-setup:
  Instalado: 3.30.0-1ubuntu3
  Candidato: 3.30.0-1ubuntu3.1
  Tabela de versão:
     3.30.0-1ubuntu3.1 500
        500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
 *** 3.30.0-1ubuntu3 500
        500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-initial-setup 3.30.0-1ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 27 11:12:31 2018
ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup
InstallationDate: Installed on 2018-11-27 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for your bug report. Do you get any details on the error?
1. could you add your journalctl log after getting the issue?
2. do you get any error printed on the command line if you start gnome-initial-setup from there?
3. does it work to add those from gnome-control-center?

[Matheus Reich (matheusr98)]

1 - I've added the journalctl log for the first boot of this computer, which is when gnome-initial-setup runs automatically.

2 - It seems that I cannot run gnome-initial-setup, the Terminal presents a error message saying:
"gnome-initial-setup: command not found"

3 - The exact same thing happens on gnome-control-center, it never loads the log-in screens.

[Sebastien Bacher (seb128)]

gnome-control-center having the same issue makes sense (no need to test again g-i-s, but just for the record it's not in the standard directory so the full path needs to be used, '/usr/lib/gnome-initial-setup/gnome-initial-setup')

Do you have any error/warning on the command line if you start gnome-control-center from there? is your internet connection working fine otherwise?

[Matheus Reich (matheusr98)]

Ok, so , I've executed both g-i-s and gnome-control-center from the terminal, and all I've got was (on both g-i-s & g-c-c):

:~$ gnome-control-center (or /usr/lib/gnome-initial-setup/gnome-initial-setup)

(gnome-control-center:9879): Clutter-WARNING **: 22:02:39.314: Whoever translated default:LTR did so wrongly.

^C

I also found that both Foursquare and Pocket log-in screens loaded without a problem, but Flickr didn't even presented a window. So the issue with the Google Account and Microsoft Account still persist. I've talked with some friends of mine, and they said that the same problem occurred with them, so this is affecting multiple users. I don't know if my region has something to do with it, since it is trying to load the Portuguese version of both log-in screens.

If you need anymore info, I'm happy to cooperate with you.

[Matheus Reich (matheusr98)]

I`m now running a virtual machine with "disco" and i`ve been able to connect all of my accounts without a problem. This bug seems to be affecting mainly "cosmic" (I don't know about "bionic"). So, it seems like the issue has been fixed on "disco", or my install of "cosmic" has a problem. But it is interesting that this is affecting some colleagues of mine, so it looks like the issue is not on my install of "cosmic".

[Sebastien Bacher (seb128)]

Hum, do you use the same locale in the vm? Did you try a cosmic in a VM? Disco didn't have much changes in its desktop stack yet so it would weird to have it fixed there. Could have to do with the translations maybe? Could you try on your machine by switching the language to english?

[Matheus Reich (matheusr98)]

So, i changed the language to english on my machine, but the same thing happens, it just won't load the page. And yes, i used the same machine to run the VM. I'm downloading the 18.10 ISO to install in a VM and see if it loads there. But this is a interesting situation, because it loads in a VM (at least in "disco"), but not the real machine. I'm going to test it on the new 18.10 VM and post any new comments here.

[Matheus Reich (matheusr98)]

I should note that the page does "load", but it takes around 4 to 5 minutes to get anything on the screen. After the wait, when something shows in the screen, I type my username, and proceed to type my password it says that an error has ocurred. On the VM ("disco" VM) there is no wait time, and everything happens without a hitch. I'll test now with the "cosmic" VM.

[Matheus Reich (matheusr98)]

Ok, i've found that problem I was having had to do with IPv6 connectivity. Usually I disable the IPv6 connection because there are certain PPAs (archive.ubuntu.com, for example) that for some odd reason, never load, and they timeout on "sudo apt update". My network provider has no problem with the IPv6 service, but Ubuntu, usually, cannot load a PPA through IPv6. Because of that, I only allow IPv4 connectivity to be active, and that was the issue. It seems that g-i-s and g-c-c only want to connect via IPv6, even though it was disabled through the g-c-c. I think that both should first check on how the network is setup up and then load the webpages as determined by the settings. That is the issue. I hope it gets fixed.

After I set IPv6 method to "Auto", both g-i-s and g-c-c loaded all log-in pages without a problem.

[Sebastien Bacher (seb128)]

Thank you for the debugging. I don't think goa requires IPv6, could you give details on how you disabled IPv6? Maybe doing the same steps is enough for others to reproduce the issue.
The issue connecting to ppas when IPv6 is enabling is a bug by itself, either in the software or in your local network configuration

[Matheus Reich (matheusr98)]

Yes, that wouldn't be a problem.

Steps:

1 - Open the GNOME Control Center (Ubuntu Settings, or Configurations);

2 - Select "Network" on the left sidebar;

3 - Press the small cog-wheel (Network Configurations);

4 - Select the IPv6 tab;

5 - On IPv6 Method, select disabled (on my system, it is on Automatic);

After that, GOA doesn't load the login screens that I've detailed on earlier comments.