After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 775488 - Cannot connect with a Gmail account
Cannot connect with a Gmail account
Status: RESOLVED DUPLICATE of bug 713744
Product: geary
Classification: Other
Component: accounts
master
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-12-01 19:13 UTC by Gautier Pelloux-Prayer
Modified: 2018-04-21 01:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gautier Pelloux-Prayer 2016-12-01 19:13:58 UTC
I created a new gmail account for bug 775215, but once I tried to use it inside Geary using the assistant it yielded at me "invalid password or username".

I also received an email on this gmail account, stating:

> Are you the one who tried signing in?
> Google will continue to block sign-in attempts from the app you're using because it has known security problems or is out of date. You can continue to use this app by allowing access to less secure apps[1], but this may leave your account vulnerable.
[1] https://support.google.com/mail/answer/7126229?visit_id=1-636162160228992067-3934614699&rd=2#cantsignin

I add to disable the security thing which is pretty bad. I guess we seriously need to update Geary to match latest Gmail security enforcements otherwise new users won't be able to login.
Comment 1 Michael Gratton 2016-12-01 23:49:51 UTC
Indeed. To address this properly in Geary we need to support OAuth2 (Bug 746705).

We do currently mention this in the FAQ: https://wiki.gnome.org/Apps/Geary/FAQ, but there seems to be two different workarounds that Google provides, depending on some hidden aspect of your account - allowing "insecure" login or adding app-specific passwords.

Note that Google's use of "insecure" here is completely farcical, it's simply marketing to ensure people pressure app vendors into supporting their proprietary extensions.
Comment 2 Gautier Pelloux-Prayer 2016-12-02 09:39:49 UTC
OK, I just wanted to be sure that this bug was reported. 

Should bug 746705 be a major blocker for the next release (if so we can close this bug).

I would not expect many users to actually reach the FAQ to understand why they cannot login (given the fact that Geary is not actually telling the correct error message). 

Otherwise we should provide a prober error message if nobody is working on 746705 for the next release?
Comment 3 Federico Bruni 2017-12-17 09:33:40 UTC
Indeed, the message error is misleading. We should warn the user to allow less secure app in Google settings.

Here's the log while trying to add a Gmail account with "less secure" app not allowed:

 [deb] 10:28:46 13,662105 imap-client-session.vala:1707: [0000/imap.gmail.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_CONNECTING] Connected to imap.gmail.com/default:993
 [deb] 10:28:46 0,000014 imap-client-session.vala:779: [0000/imap.gmail.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_CONNECTING] Connected
 [deb] 10:28:46 0,075249 imap-client-session.vala:1780: [0000/imap.gmail.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_NOAUTH] capability #1: NAMESPACE IMAP4rev1 X-GM-EXT-1 XYZZY "AUTH=OAUTHBEARER" "AUTH=PLAIN" "AUTH=XOAUTH" "AUTH=PLAIN-CLIENTTOKEN" "AUTH=XOAUTH2" UNSELECT SASL-IR CHILDREN XLIST QUOTA ID IDLE
 [deb] 10:28:46 0,002728 imap-client-session.vala:873: [0000/imap.gmail.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_NOAUTH] use_starttls=false is_ssl=true starttls=false
 [deb] 10:28:46 0,000010 imap-client-session.vala:901: [0000/imap.gmail.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_NOAUTH] No STARTTLS attempted
 [deb] 10:28:48 1,124017 imap-client-session.vala:1295: [0000/imap.gmail.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_AUTHORIZING] Received error from server: * NO [WEBALERT https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbvEB3W194Uf2iMnMIx5wWURJIIsutw-_yc4gTyNrH5kEKNIHo-D_YQ_0fdqXPRek8r3-RidXz5-AA7JSFGII30gf2fXWvvl1B9H9vdS4XfSMQRvri_haiKZk52fyoelvnECR5z1kI7kFuOtrJa1DPBG0nvYg72L3kVfYYUMEWV71BtwiVMlC7lgi51mOYEzf-_8lQSDMYDs6mRiYC6SarVAiedAYp-P5EmHroYf3Ycq97vBgfo] Web login required.
 [deb] 10:28:48 0,000387 imap-client-session.vala:1056: [0000/imap.gmail.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_AUTHORIZING] Unable to LOGIN: a002 NO [ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)
 [deb] 10:28:48 0,000241 geary-engine.vala:348: Error validating IMAP account info: Unable to login to 0000/imap.gmail.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_NOAUTH with supplied credentials
 [deb] 10:28:48 0,000275 imap-deserializer.vala:252: [des:0000/GEARY_IMAP_DESERIALIZER_STATE_CLOSED] Deserializer closed
 [deb] 10:28:48 0,000047 imap-client-connection.vala:434: [0000/imap.gmail.com/default:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED] Disconnecting...
 [deb] 10:28:48 0,000284 imap-client-connection.vala:437: [0000/imap.gmail.com/default:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED] Disconnected
 [deb] 10:28:48 0,000021 imap-client-session.vala:1713: [0000/imap.gmail.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_BROKEN] Disconnected from imap.gmail.com/default:993
 [deb] 10:28:48 0,000287 imap-client-session.vala:487: DTOR: ClientSession imap.gmail.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_BROKEN
 [deb] 10:28:48 0,419214 smtp-client-session.vala:102: [smtp.gmail.com/default:465] Attempting PLAIN authenticator
 [deb] 10:28:48 0,405723 smtp-client-session.vala:102: [smtp.gmail.com/default:465] Attempting LOGIN authenticator
 [deb] 10:28:49 0,459196 geary-engine.vala:369: Error validating SMTP account info: Unable to authenticate with smtp.gmail.com/default:465
 [deb] 10:28:49 0,101199 geary-controller.vala:759: Validation failed. Prompting user for revised account information
Comment 4 Michael Gratton 2018-02-07 03:39:46 UTC

*** This bug has been marked as a duplicate of bug 746705 ***
Comment 5 Michael Gratton 2018-04-21 01:43:22 UTC
As Federico pointed out, this is actually a duplicate of Bug 713744.

*** This bug has been marked as a duplicate of bug 713744 ***