KDE-Forum.org

works for me:


user: username@gmail.com
pass: yourpassword

Use SSL
Allow plain text
Override default server information:
talk.google.com 5223

Works for me too.

I just had to install qca and qca-tls rpms in order to be able to use SSL. Everything else worked when configured as they say on their website for Gaim or Psi.

_______
nonick.

it seems that there are some problems with the contact list.

1. i cannot add a contact (using Kopete)
2. if i send a mail using gmail a contact is added and it seems that if I delete the contact from Kopete it also deletes the entry in my Gmail addressbook.it hapened to me and to a friend of mine as well.

anyone having the same problems?
I was using kopete 0.10.0 in the meantime upgraded to 0.10.3, I don't know if 0.10.3 does the same.

It is said everywhere that Google Talk works in Kopete if you enter port 5223, SSl etc., but although it connects fine for me (with a warning about Google's certificate which I also get with Psi), every time I speak to somebody who uses Google's official client I make him fall and go offline. I appear on their buddy list and so do they, we can open a window and start a chat, they write and I see their messages, but when I write something the other person gets thrown away. This doesn't happen when I use Gaim (which takes several attampts to connect), it works ok.

On the other hand, I have been able to speak to a Mac user using iChat with my Kopete. Everything went mooth.

So, does anything like this happen to you? Can you help me stop being kind of an IM-terrorist? By the way, just in case it helps, I'm behind a router with ADSL connection. I'm using Kopete 0.10.3 on KDE 3.4.2, SuSE 9.3

I have the same problem

i'm having the same problem, not tested yet with users using another cliënt tough

This thread got me connected. Needed that SSL turned on.

However, I have the same problem where it appears that anytime I start typing, I end up kicking the person I am talking to offline. They rejoin and send a message that opens a new chat window. Very annoying. I'm using gaim at the moment, but sure would like to get back to Kopete for Google Talk.

Any news on this bug?

Thanks,

Eric

http://wiki.kde.org/tiki-index.php?page=Google+Talk+support

Quoted

Unfortunately talking to windows google talk clients from kopete seems to make them disconnect.
It is a problem with the google client failing to properly parse part of the message sent by kopete (the typing notification).
That's because Kopete 0.10 send Typing notification, even if they are not requested.
This is fixed in Kopete 0.11 which will be released with KDE 3.5. This seems fixed in Google Talk Client 1.0.0.68

I'd suggest that you have your friends upgrade their Google Talk client now. A friend of mine is using 1.0.0.70. I can keep talking with him using Kopete.

Thanks for the notice, dalhard. It's working great now. My wife's google talk client apparently updated itself. It's at 1.0.0.70 now.

I am using Kopete 0.9.0 on KDE 3.3.0, and I can't change my port to 5223. The box is grayed-out. I havn't been able to find any other posts relating to this. If anyone has any suggestions, it would be greatly appreciated.

Quoted

I am using Kopete 0.9.0 on KDE 3.3.0, and I can't change my port to 5223. The box is grayed-out. I havn't been able to find any other posts relating to this. If anyone has any suggestions, it would be greatly appreciated.

You'll need a newer version. 0.10.x will work on KDE 3.3.0 and the upcoming 0.12 beta will compile on KDE 3.3.x although not all features will be working (emoticons were moved to kdelibs in KDE 3.4 so those won't be shown graphically)

A bit of a late contribution to this thread, but I get the following message when connecting to Jabber with my gmail.com address:

Quoted

The certificate of server talk.google.com could not be validated for account myaddress@gmail.com: The Certificate Authority is invalid.

I sincerely doubt someone is trying to spoof me, but why is this error occurring and is there anything I can do to fix it?

Many thanks,

-- Joe

i believe that this happens since QCA does not use the normal KDE way of validating certificates and since it doesn't know about it, it can't validate it.

Hello,
I am having the same problem with trying to select a port other than 5222. I am using Kopete 0.10 / KDE 3.4.0 on Kubuntu. Does anyone know of a solution?