Bug 111418 - jabber plugin: does not connect to gmail talk
Summary: jabber plugin: does not connect to gmail talk
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: 0.10.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-24 14:02 UTC by gallir
Modified: 2005-08-26 09:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gallir 2005-08-24 14:02:10 UTC
Version:           0.10.2 (using KDE 3.4.1, Debian Package 4:3.4.1-1 (3.1))
Compiler:          gcc version 3.3.6 (Debian 1:3.3.6-5)
OS:                Linux (i686) release 2.6.12

Google just started its Jabber services at talk.google.com. Kopete is unable to authenticate, it seems to me is related to TLS encription. I have  qca-tls package installed.

I understand kopete uses same PSI libreries and methods, psi does not work neither, so I'm not sure is a distro problem (Debian Sid, kde 3.4.1) or a general one.

How can I get more useful debug information?
Comment 1 Matt Rogers 2005-08-24 14:06:51 UTC
make sure you set it up correctly: http://wiki.kde.org/tiki-index.php?page=Google+Talk+support
Comment 2 gallir 2005-08-24 14:19:07 UTC
I tried before but it gives the following error:

"There was a Transport Layer Security (TLS) error: Failed to establish a secure connection."
Comment 3 gallir 2005-08-24 14:26:22 UTC
The previous error message occurs when port 5222 is specified, with port 5223 there is no answer from the server:

antoli:~# tcpdump -n port 5223
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes

14:23:55.207819 IP 192.168.0.10.55149 > 64.233.167.125.5223: S 4213766553:4213766553(0) win 5840 <mss 1460,sackOK,timestamp 152790686 0,nop,wscale 2>

14:23:58.207631 IP 192.168.0.10.55149 > 64.233.167.125.5223: S 4213766553:4213766553(0) win 5840 <mss 1460,sackOK,timestamp 152793687 0,nop,wscale 2>

14:24:04.206585 IP 192.168.0.10.55149 > 64.233.167.125.5223: S 4213766553:4213766553(0) win 5840 <mss 1460,sackOK,timestamp 152799687 0,nop,wscale 2>
Comment 4 Blindauer Emmanuel 2005-08-24 14:40:37 UTC
It works fine here for me, you have a problem on your side.
Comment 5 gallir 2005-08-24 14:47:33 UTC
OK (but I'm not the only one), but what's the problem? How can I gather more information of where is the error? 

Which version do you have? 3.4.x?

Comment 6 Nicolas L. 2005-08-24 17:08:14 UTC
it works well for me with kopete 0.10.3


have you qca-tls installed ?
Comment 7 Olivier Goffart 2005-08-24 17:34:55 UTC
*** Bug 111426 has been marked as a duplicate of this bug. ***
Comment 8 gallir 2005-08-24 18:29:27 UTC
Mine in 0.10.2 and qca-tls is 1.0-1 (debian).
 
Comment 9 Aaron Williams 2005-08-24 20:23:33 UTC
It's working for me with 0.10.3 and qca-1.0.9, however every time someone types something it thinks it's a new session and opens a new tab.
Comment 10 jorgeml 2005-08-25 09:37:40 UTC
It seems that from time to time Google Talk users change their resource, i.e. jorgeml@gmail.com/talk.random_string_that_changes , that makes Kopete think that the other party logged off and logged in.
Comment 11 gallir 2005-08-25 14:21:48 UTC
Today my kopete started to work, it seems that port 5223 is being open progressively on google servers.
Comment 12 Olivier Goffart 2005-08-26 01:17:15 UTC
Kopete can only connect to google on port 5223
it's because of a not implemented feature in libiris
http://psi-im.org/wiki/FAQ#What_is_this_SSL.2FTLS_thing_I_keep_hearing_about.3F

As it's already a known libiris bug, i'll close this report
(Kopete uses libiris)

Comment 13 jorgeml 2005-08-26 08:44:34 UTC
What about the issues in comments #9 and #10, should we open another bug? It makes talking to people using Google's client quite annoying. I'm using 0.10.2.
Comment 14 Olivier Goffart 2005-08-26 09:21:02 UTC
yes open another bug.