Gtalk does not work in gajim 0.15 (Quantal)

Bug #1059756 reported by Andrew Nenakhov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gajim (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Seems like a related problem to https://trac.gajim.org/ticket/6867.

Before update, Gajim would sometimes refuse to connect to Gtalk, now it does not connect at all. When XML console is opened up, i see the following:

 (i use it in russian locale, so exact wording might be different in EN, but i think it's not important)
Authentication Error "redsolution.ru"
Please check your login and password for correctness.

XML console has this:
<!-- Out -->
<?xml version='1.0'?>
<stream:stream xmlns="jabber:client" to="redsolution.ru" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xml:lang="ru" >

<!-- In -->
<stream:stream from="redsolution.ru" id="B78C12C023E680F3" 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>

Other XMPP servers seem to work fine. Empathy is affected too, Pidgin works fine.

Tags: gajim gtalk xmpp
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gajim (Ubuntu):
status: New → Confirmed
Revision history for this message
Marc D. (koshy) wrote :

Version: 0.15-1.1

I have the same problem with an original GMail account since upgrading from precise to quantal. The error message is:

  Authentication failed with "gmail.com"
  Please check your login and password for correctness.

The problem does not occur with the same version of gajim in Debian wheezy.

Debug output:

<!-- Out -->
<?xml version='1.0'?>
<stream:stream xmlns="jabber:client" to="gmail.com" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xml:lang="en" >

<!-- In -->
<stream:stream from="gmail.com" id="CC617F05CF21C9D9" 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>

Revision history for this message
Andrew Nenakhov (andrew-nenakhov-redsolution) wrote :

The issue seems to be fixed after latest update & reboot. All Gtalk accounts work OK now in Gajim.

Revision history for this message
Marc D. (koshy) wrote :

Indeed, it works now, although there was no update of gajim. There is also no difference in the server replies.

gajim just initiates starttls now instead of throwing an error:

<!-- Out -->
<?xml version='1.0'?>
<stream:stream xmlns="jabber:client" to="gmail.com" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xml:lang="en" >

<!-- In -->
<stream:stream from="gmail.com" id="99A425FE4FF99C8B" 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>

<!-- Out -->
<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>

Revision history for this message
Forest (foresto) wrote :

Pidgin sometimes (correctly) complains that the TLS certificate offered by talk.google.com is for a different domain: gmail.com. The fact that it only happens sometimes implies that Google's servers are using any of several certificates seemingly at random. This could be why you guys are seeing Gajim sometimes fail with Google Talk.

Revision history for this message
Andrew Nenakhov (andrew-nenakhov-redsolution) wrote : Re: [Bug 1059756] Re: Gtalk does not work in gajim 0.15 (Quantal)

No, that is a separate issue, not the one I was reporting. Issue with
rotating certificates is a valid consequence of Google's setup.

Revision history for this message
Daniel (wurstsalat3000) wrote :

GTalk was closed.

Changed in gajim (Ubuntu):
status: Confirmed → Invalid
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.