Red Hat Bugzilla – Bug 432132
Kopete 0.50.1 does not connect to google talk / jabber
Last modified: 2015-07-13 13:37:16 EDT
Description of problem:
Kopete (0.50.1; kde4.0.1) can't connect with SSL/TLS encripted jabber (google
talk). I don't even get the certificate authorization request.
Version-Release number of selected component (if applicable):
Try using Kopete (0.50.1) with jabber/google talk
After a while the protocol is offline
Successful connection through the gtalk account
I've also tried to use kopete 0.50.1 on a Kubuntu with kde 4.0.1 - it worked.
So I guess the Problem can be in the QCA / OSSL plugin.
I don't know if it might be useful, but kopete says MSN was connected
successfuly (I had no online contacts, so not sure if it realy worked)
Created attachment 294437 [details]
Kopete output when connecting to google talk / jabber
Same here, installed qca-tls-1.0-13.fc9.x86_64 but didn't help. Looks like the
plugin is required.
Also, MSN is not connecting. It is working fine on my FC8 system and with
Windows system using Pidgin, but doesn't work with kopete 0.50.1.
AIM, ICQ and non-SSL jabber accounts work fine.
*** Bug 436972 has been marked as a duplicate of this bug. ***
resolves SSL message and jabber.org session connects;
however, googletalk and MSN still receive
"connecting" and then disconnect. No other message
gtalk is known to not work, see also upstream report:
Hmm, connecting to Jabber/Gtalk definitely works for me.
Created attachment 297618 [details]
Kopete GTalk working
are you running rawhide or F8? I'm running F9 (rawhide) - so that may be the
Just retested with kdenetwork-4.0.3-4.fc9.x86_64
Googletalk does not connect.
Using: talk.google.com and port 5223
Have SSL and Plain text authentication selected.
Interesting to note however that I am able to connect to jabber.org using SSL
I have no problems connecting to googletalk under F8 with kopete. Am able to
connect under F9 using PIDGIN client with no issues.
Problem is not fixed, but closed->upstream, which means only we're continuing to
track it there (not here). Please make further comments there:
*** Bug 445117 has been marked as a duplicate of this bug. ***
I'm testing a fix for that
kdenetwork-4.0.4-4.fc9 has been submitted as an update for Fedora 9
kdenetwork-4.0.4-4.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
So can we close this as fixed or does this still happen with current 4.1.x?
It works for me since quite a while (June I think)... So I guess this issue can be closed