This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Issues with Kopete 1.3.0 with KDE 4.9 and Jabber/Google Talk

Tags: None
(comma "," separated)
vikrant82
Registered Member
Posts
22
Karma
0
OS
I am having issues logging into google chat/talk with kopete 1.3.0, shipped with KDE 4.9. I am using kubuntu. I have filed a bug - 303268 - https://bugs.kde.org/show_bug.cgi?id=303268 for the same.

I have tried with new accounts, all server addresses and configs.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
I have responded to your bug report.
Initially I got the same behaviour until enabling SSL to server talk.google.com, port 5223.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
vikrant82
Registered Member
Posts
22
Karma
0
OS
Can you post your environment details. Unfortunately, I have tried that already. Facing same issues. If run through console : All I get is:

Unknown signature value: 668
Unknown signature value: 668
Unknown signature value: 668
Unknown signature value: 668
Unknown signature value: 668
Unknown signature value: 795
Unknown signature value: 668
Unknown signature value: 795
Unknown signature value: 668
Unknown signature value: 668
Unknown signature value: 669
Unknown signature value: 795
Unknown signature value: 668
Unknown signature value: 668
Unknown signature value: 668
Unknown signature value: 668

I am reporting the issue on: Kopete 1.3.0 using KDE 4.9.00.

ii kopete 4:4.9.0-0ubuntu3 amd64 instant messaging and chat application
ii kopete-message-indicator 0.2.1-0ubuntu2 amd64 Kopete plugin for Message Indicator
ii libkopete4 4:4.9.0-0ubuntu3 amd64 main Kopete library
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
I am running Trunk KDE, which includes Kopete.
Unfortunately those console messages are not helpful.

On the Basic Setup tab, Jabber ID is my @gmail.com address, and "Exclude from connect all" is checked.
Connection tab: Use protocol encryption and Allow plain-text password authentication are both checked.
Override default server information is also checked, with server talk.google.com and port 5223 specified.
Google Talk tab: Enable Google Talk libjingle support is enabled.
Privacy: Hide system and client info is checked.

I just disconnected and reconnected it without trouble.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
vikrant82
Registered Member
Posts
22
Karma
0
OS
Nope! Tried with those. Only setting I had different was I didnt have "Hide system and client info.. "

I am suspecting some conflicting library. I have lots of telepathy stuff installed. However, telepathy is connecting just fine.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
This is highly unusual. If there was a conflicting library the problem would appear to be much greater due to the way Kopete is built. One guess could be that Google do not permit two Jabber clients to be connected simultaneously from the same IP address to the same account? (Or that they fight over the account somehow).


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
vikrant82
Registered Member
Posts
22
Karma
0
OS
But I am not connecting them together. One at a time. It doesn't seem to be a config problem. I have tried with various google accounts, with different system accounts, even with two different machines. I will try to sniff out network traffic when kopete tries to connect and see if there's a connect to google at all.
[EDIT]: Yup there's definitely stuff happening over wire to talk.l.google.com over to 5223. But can't login.
vikrant82
Registered Member
Posts
22
Karma
0
OS
OK! I tried with another system where same version was able to connect. This particular system has KDE 4.9 installed on precise. The system where it doesn't work is Quantal. So it means there are some updated quantal libs which broke this.

Ben, How are you running trunk KDE ? Neon ? Which distro/version are you on ?
vikrant82
Registered Member
Posts
22
Karma
0
OS
Just to confirm.. I upgraded the system with KDE 4.9 from precise to quantal and kopete stops working.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
I use openSUSE 12.1, and self compile KDE from upstream sources.

As this breaks only when you upgrade to Quantal, I suggest you file a bug against Ubuntu, as the fault exists in an underlying library there.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
vikrant82
Registered Member
Posts
22
Karma
0
OS


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]