Invalid Credentials

Bug #692851 reported by Mike Serendy
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
GMail Notifier
Incomplete
Undecided
Unassigned
Arch Linux
New
Undecided
Unassigned

Bug Description

Seems like this bug has been reintroduced hence the new bugreport for an old problem.
I "upgraded" from Ubuntu 10.10 32-bit where gm-notify worked fine to
Ubuntu 10.10 64-bit. Now i get Invalid Credentials.

IMAP is enabled also i'm 99.9% certain i used the correct Credentials

Revision history for this message
Wolfgang Betz (wbetz) wrote :

Ubuntu 11.04 x86_64 GNU/Linux
... same problem for me.

Revision history for this message
sab (sab-dreamflow) wrote :

Ubuntu 11.04 i686 GNU/Linux

Likewise. And yes, imap is enabled and working, since I use it in Thunderbird on multiple computers.

Revision history for this message
Alexander Hungenberg (alexander-hungenberg-gmail) wrote :

interesting... Currently I don't remember any platform specific code in gm-notify, so if this problem really exists, it must have it's source in the underlying libs.

Could you please activate the debug mode by setting
_DEBUG = True
in line 28 of file /usr/lib/python2.*/dist-packages/gtalk.py and post the output of gm-notify running in a terminal?

Thank you!

Changed in gm-notify:
status: New → Incomplete
Revision history for this message
sab (sab-dreamflow) wrote :

Voila; (username deleted, but confirmed to be my actual username)

> <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' to='[my actual username here]' version='1.0'>
< <stream:stream from="[my actual username here]" id="368B5D410A4C4B1F" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"><stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>X-GOOGLE-TOKEN</mechanism><mechanism>X-OAUTH2</mechanism></mechanisms></stream:features>
> <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
< <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
> <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' to='[my actual username here]' version='1.0'>
< <stream:stream from="[my actual username here]" id="A3CB92D5A58702C7" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
< <stream:features><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>X-GOOGLE-TOKEN</mechanism><mechanism>X-OAUTH2</mechanism></mechanisms></stream:features>
disconnected
disconnected

Revision history for this message
Sebastian Gaul (n-admin-mgvmedia-com) wrote :

Think this is the same problem: I cannot log in anymore since using Ubuntu 11.04.

This is probably a problem with my latest password change. I tried to enter the new one, but all "Invalid Credentials" was the answer. Is there a problem with the password field? My password is considerably longer than 20 signs and contains several special characters including spaces etc. Can this be a problem?

Revision history for this message
Sebastian Gaul (n-admin-mgvmedia-com) wrote :

I don't know why, but suddenly it works again on both my computers.

Revision history for this message
matt r (mat-r) wrote :

I'm getting the same problem with my google apps account. If I enter the full username ( including @domain) and password it claims I have entered 'Invalid credentials'. Interestingly, it works for my other gmails (not google apps) account, which has the same password.

Let me know if I can produce any useful output.

Revision history for this message
matt r (mat-r) wrote :

My problem turned out not to be a bug - I needed to enable google chat for my domain before it would allow me to log in.

Revision history for this message
Anders Honoré (b9anders) wrote :

I installed this on Arch Linux yesterday and have this bug. Is there no way to troubleshoot this?

I have unlocked the captcha, made sure Imap is enabled, checked with different google accounts and re-compiled the app, and there don't seem to be any more suggested advice.

Revision history for this message
Hannes Magnusson (bjori) wrote :

Could this have anything to do with 2 step verification?

I'm also experiencing this problem on Xubuntu 12.04 :(

Revision history for this message
Hannes Magnusson (bjori) wrote :

> <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' to='gmail.com' version='1.0'>
< <stream:stream from="gmail.com" id="2BD20F1490B3EB34" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"><stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>X-GOOGLE-TOKEN</mechanism><mechanism>X-OAUTH2</mechanism></mechanisms></stream:features>
> <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
< <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
> <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' to='gmail.com' version='1.0'>
< <stream:stream from="gmail.com" id="A424B3C215E5532F" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
< <stream:features><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>X-GOOGLE-TOKEN</mechanism><mechanism>X-OAUTH2</mechanism></mechanisms></stream:features>
> <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN'>AGhhbm5lcy5tYWdudXNzb24Abm8sIHRoaXMgaXNuJ3QgYWN0dWFsbHkgdGhlIHBhc3N3b3JkIDop</auth>
< <failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-authorized/></failure>
disconnected
< </stream:stream>
disconnected

here is my raw debug output

Revision history for this message
Dmitrij (php5engineer) wrote :

Sign-in attempt prevented
Someone just tried to sign in to your Google Account from an app that doesn't meet modern security standards.
We strongly recommend that you use a secure app, like Gmail, to access your account. All apps made by Google meet these security standards. Using a less secure app, on the other hand, could leave your account vulnerable.
https://support.google.com/accounts/answer/6010255

Revision history for this message
Thomas Wehr (derwehr) wrote :

To use GM-Notify you have to activate "less-secure Apps" through this link:
https://www.google.com/settings/security/lesssecureapps

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.