FS#34404 - [gajim] can't connect to gtalk

Attached to Project: Arch Linux
Opened by Gwen Lune (gwenlune) - Thursday, 21 March 2013, 22:08 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 27 March 2013, 14:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
It's not possible to connect to gtalk with new version of gajim. There's nothing in the xml console

here are some traces with the verbose option :
2:49:36 (D) gajim.c.gnupg gpg --status-fd 2 --no-tty --version
22:49:36 (D) gajim.c.gnupg stderr reader: <Thread(Thread-28, initial daemon)>
22:49:36 (D) gajim.c.gnupg stdout reader: <Thread(Thread-29, initial daemon)>
22:49:36 (D) gajim.c.gnupg chunk: 'gpg (GnuPG) 2.0.19\nlibgcrypt 1.5.0\nCopyright (C) 2012 Free Software Foundation, Inc.\nLicense GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to t'
22:49:36 (D) gajim.c.resolver resolve _xmpp-client._tcp.gmail.com type=srv
22:49:36 (D) gajim.c.resolver Starting to resolve _xmpp-client._tcp.gmail.com using <common.resolver.DrillResolver instance at 0x1d68d40>
22:49:36 (I) gajim.c.x.idlequeue read timeout set for fd 23 on 20 seconds
22:49:36 (I) gajim.c.x.idlequeue read timeout removed for fd 23
22:49:36 (I) gajim.c.x.idlequeue read timeout removed for fd 23
22:49:36 (D) gajim.c.resolver Resolving result for _xmpp-client._tcp.gmail.com: []
22:49:36 (D) gajim.c.connection Connection to next host
22:49:36 (I) gajim.c.connection >>>>>> Connecting to gmail.com [gmail.com:5222], type = tls
22:49:36 (I) gajim.c.x.plugin Plugging <common.xmpp.transports_nb.NonBlockingTCP instance at 0x2cb1c68> __INTO__ <common.xmpp.client_nb.NonBlockingClient instance at 0x2cb1a70>
22:49:36 (I) gajim.c.x.transports_nb NonBlockingTCP Connect :: About to connect to 173.194.45.54:5222
22:49:36 (I) gajim.c.x.transports_nb Plugging fd 23, W:True, R:False
22:49:36 (I) gajim.c.x.idlequeue read timeout set for fd 23 on 30 seconds
22:49:36 (I) gajim.c.x.transports_nb After NB connect() of 46865512. "Opération maintenant en cours" raised => CONNECTING

Additional info:
* package version(s) 0.15.3-1
This task depends upon

Closed by  Eric Belanger (Snowman)
Wednesday, 27 March 2013, 14:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  gajim-0.15.3-2 is now in [extra]
Comment by Gaetan Bisson (vesath) - Thursday, 21 March 2013, 22:34 GMT
What is the output of `drill srv _xmpp-client._tcp.gmail.com`?
Comment by Gwen Lune (gwenlune) - Thursday, 21 March 2013, 22:35 GMT
drill srv _xmpp-client._tcp.gmail.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 25794
;; flags: qr rd ra ; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; _xmpp-client._tcp.gmail.com. IN SRV

;; ANSWER SECTION:
_xmpp-client._tcp.gmail.com. 451 IN SRV 20 0 5222 alt2.xmpp.l.google.com.
_xmpp-client._tcp.gmail.com. 451 IN SRV 20 0 5222 alt3.xmpp.l.google.com.
_xmpp-client._tcp.gmail.com. 451 IN SRV 20 0 5222 alt1.xmpp.l.google.com.
_xmpp-client._tcp.gmail.com. 451 IN SRV 5 0 5222 xmpp.l.google.com.
_xmpp-client._tcp.gmail.com. 451 IN SRV 20 0 5222 alt4.xmpp.l.google.com.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 32 msec
;; SERVER: 192.168.0.254
;; WHEN: Thu Mar 21 23:35:32 2013
;; MSG SIZE rcvd: 250
Comment by Gaetan Bisson (vesath) - Thursday, 21 March 2013, 23:54 GMT
That's fine. The problem is most likely in the python DrillResolver then. I can look into it Wednesday (no Internet access for me until then) if it is still pending then.
Comment by Gaetan Bisson (vesath) - Wednesday, 27 March 2013, 05:29 GMT
My ldns patch had a stupid typo. It's fixed in gajim-0.15.3-2 from [testing]. Could you confirm that it solves your problem?
I'll leave it to Eric to move it to [extra].
Comment by Gwen Lune (gwenlune) - Wednesday, 27 March 2013, 06:08 GMT
It's ok for me, thanks!

Loading...