GNOME Bugzilla – Bug 781990
Cannot sign in with new Google sign-in page
Last modified: 2017-05-18 18:40:51 UTC
I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. I experienced this on Ubuntu Gnome 16.10 and 17.04, but others have reported the same issue on different distros, too. Here's the Launchpad/Ubuntu-Gnome thread with more details and reports: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019
I think this is due to the change on Google login page --- As google is stated on the login form.
Created attachment 350786 [details] Google stated changes happened to login form
Created attachment 350787 [details] Blank page appear on Online Account login for Google Acocunts
I found a work around but you need an iPhone or Android Phone setup the google app to login to services. Once I enabled on my iphone when login in to google online accounts in gnome3 it comes up with a 2 step verification number which then entered on my phones google app then logs in and by passes the blank screen in gnome3 and I am now sucessfully logged in to google services. I did this on debian stretch
I enabled 2 step verification for my Google account and tried again. Didn't work, same problem (blank window after entering the password).
I have this problem too. I think Gnome don't support 2 step verification. When I used it with 2 step verification(about 3 month ago) it always forgot the login and I should login again. So I disabled.
My bad it is not 2-step verification that works. Turn that off in your google accounts setup. The function you need is to use your phone to login instead of typing a password. https://support.google.com/accounts/answer/6361026?hl=en Once enabled I opened gnome online accounts and added my google account and normally where you enter your password the google app on my iphone alerted me and using touch id it then allowed me to login and was no longer presented with the blank white login window. One caveat with this setup. for some reason google dont allow you to setup up app specific passwords unless you have 2-step verification turned on. So to get google online accounts working on my debian setup with gnome3 I had turn on goolge's 2 step verification to generate an app specific password for my gmail client 'geary'. Then logged back into my google account turned off 2 step verification and setup use my phone to login. This does not revoke any app specific passwords. Then goto gnome online accounts and setup your google account. When prompted use your touch id on your phone. Everything is now working.
This is true but still not solve the problem for people login using password and 2 factor authentication. There are many cases especially business/company google account required 2 factor authentication. In 2 factor authentication also have Google Prompt on phone instead of enter the confirmation code. Anyone know how to debug and identify the root cause of the blank page? (In reply to freddypsenior from comment #7) > My bad it is not 2-step verification that works. Turn that off in your > google accounts setup. The function you need is to use your phone to login > instead of typing a password. > > https://support.google.com/accounts/answer/6361026?hl=en > > Once enabled I opened gnome online accounts and added my google account and > normally where you enter your password the google app on my iphone alerted > me and using touch id it then allowed me to login and was no longer > presented with the blank white login window. > > One caveat with this setup. > > for some reason google dont allow you to setup up app specific passwords > unless you have 2-step verification turned on. > > So to get google online accounts working on my debian setup with gnome3 I > had turn on goolge's 2 step verification to generate an app specific > password for my gmail client 'geary'. > > Then logged back into my google account turned off 2 step verification and > setup use my phone to login. This does not revoke any app specific passwords. > > Then goto gnome online accounts and setup your google account. When > prompted use your touch id on your phone. > > Everything is now working.
What freddyp stated works for google and gsuite admin accounts. There are no options to turn on "phone authentication" for gsuite non-admin accounts. This blank page really needs to be fixed.
The reason this is happening is that apparently google have changed the license page 3 days ago and therefore gnome-online accounts can't display it hence the blank white window. just to clarify the phone authentication worked for me to get passed the white window. I cannot vouch for how it works on android as I did mine with an iPhone. But yes it worked and I can reproduce it working. The reason i mentioned 2 step verification was that after enabling phone authentication I could not configure geary mail with my gmail. I then went to get an application specific password from google for geary. But you cant get one unless you turn on 2 step verification. I did that got geary working but then when i went back to gnome online accounts it has logged me out of google saying my password had expired. I then went back to google and turned off 2 step verification and turned back on phone authentication. this allowed me to log back in via gnome online accounts and geary mail carried on working.
Changing the Google login to use a phone may indeed be a useful workaround (and it did in my case). But the bug is still a show stopper for those who can't or don't want to go this way. There are many reasons against the phone workaround (don't have a recent iPhone or Android phone, no reception, etc.).
Do we know if the gnome-devs are aware of this issue? Has anyone spoken to them in IRC? I really hope we can get an emergency patch out asap to all the distros
Hello people! I have some problem with registering with Google through gnome-online-accounts 3.24.0. In the application window after entering the name, then the password is just a white screen. Registration does not work. This does not allow now to use mail (evolution, contacts) and other services integrated into the system. Other online services, like facebook, pocket, work well.
(In reply to Britt Yazel from comment #12) > Do we know if the gnome-devs are aware of this issue? Has anyone spoken to > them in IRC? I really hope we can get an emergency patch out asap to all the > distros I don't know if any of the wizards is aware of this. I have no clue how to get in touch with them. I just reported the bug and assumed this would automatically ring a bell somewhere.
Updating webkit2gtk to development version 2.17.1 doesn't help on Arch.
Debarshi is on vacation this week. He will be back on Tuesxay
*** Bug 782229 has been marked as a duplicate of this bug. ***
I added more information to this other bug report -> https://bugzilla.gnome.org/show_bug.cgi?id=782191#c1
I've read through the source and compared to the new sign-in page (unfortunately I don't have an old sign-in page for comparison). The sign-in page has an input element of type="email" with id="identifierId" and name="identifier" whereas the code appears to be expecting one of type="email" with id="Email" and name="Email" (see https://git.gnome.org/browse/gnome-online-accounts/tree/src/goabackend/goagoogleprovider.c?h=3.24.0#n283) I haven't developed GNOME (or dbus) components before and am having trouble sorting out how to build a development version for testing, so maybe someone else can try changing lines 284 and 288 to match the new sign-in page?
*** Bug 782191 has been marked as a duplicate of this bug. ***
(In reply to Joshua Randall from comment #19) > I've read through the source and compared to the new sign-in page > (unfortunately I don't have an old sign-in page for comparison). The sign-in > page has an input element of type="email" with id="identifierId" and > name="identifier" whereas the code appears to be expecting one of > type="email" with id="Email" and name="Email" (see > https://git.gnome.org/browse/gnome-online-accounts/tree/src/goabackend/ > goagoogleprovider.c?h=3.24.0#n283) > > I haven't developed GNOME (or dbus) components before and am having trouble > sorting out how to build a development version for testing, so maybe someone > else can try changing lines 284 and 288 to match the new sign-in page? I tried this but it didn't help https://paste.gnome.org/p7msecf2z Is the password field correct?
(In reply to Hussam Al-Tayeb from comment #21) (In reply to Joshua Randall from comment #19) The issue is not specific to GOA, it also happens when you try to login to a google account with epiphany. It must be some common component/library which is at fault.
The patch in https://bugs.webkit.org/show_bug.cgi?id=171770 fixes it for me.
Being that this bug has been changed to "Resolved notgnome", does this mean that the dev's are leaving this issue in the hands of Google to address and fix?
@Jesse it was fixed in WebKitGTK+ https://webkitgtk.org/2017/05/09/webkitgtk2.16.2-released.html
Ah, awesome! Thanks for the info' @Mateusz. Hoping this will get packaged and updated in Ubuntu GNOME 17.04, soon.
Confirm that this fixed the bug. Thanks very many!!!
@Jesse, for more information about this fix in Ubuntu, see the Launchpad bug mentioned in the original comment here. Most Linux distros will be packaging this update soon but it may take several days before the update is pushed out to all users.
@Jeremy, gotcha, really appreciate it sir. Thanks for the information!
*** Bug 781985 has been marked as a duplicate of this bug. ***