Bug 303268

Summary:	Kopete 1.3.0 Can't connect to Jabber/google chat
Product:	[Unmaintained] kopete	Reporter:	vikrant <vikrant82>
Component:	Jabber Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED FIXED
Severity:	major	CC:	keren_sky, munzirtaha, pali.rohar, psychonaut, siteshwar, vikrant82
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:	4.11
Sentry Crash Report:

Description vikrant 2012-07-09 22:44:31 UTC

Have tried all combinations of settings for connecting to a google account. But kopete cant connect to google chat. Logs show errors on lines of:

Unknown signature value: 668
Unknown signature value: 795
(Lots of them)

Reproducible: Always

Steps to Reproduce:
1. Add a google account.
2. Connect
3. Tries to connect and goes offline
Actual Results:  
Can't connect

Expected Results:  
Should connect

This is on KDE 4.8.90.

Comment 1 vikrant 2012-07-12 21:43:43 UTC

Any updates ?

Comment 2 Siteshwar 2012-07-20 21:56:30 UTC

I confirm this bug in Kopete 1.2.3

Comment 3 vikrant 2012-08-04 09:27:03 UTC

Same issue with kopete 1.3.0. 

"Connection problem with jabber server talk.google.com There was error authenticating with server: Login failed with unknown reason."

Comment 4 Ben Cooksley 2012-08-04 10:08:09 UTC

Open Kopete settings > Accounts, select the GMail/GTalk account > Modify Account. Select the "Connection" tab, then make sure "Use protocol encryption (SSL)" is checked. The server should be talk.google.com, port 5223.

Comment 5 vikrant 2012-08-04 10:43:20 UTC

Hello Ben, I have tried that already. 

As I already mentioned - "Have tried all combinations of settings for connecting to a google account".

Please post your environment details.. 

I am on KDE 4.9.00, Kopete 1.3.0

Comment 6 Munzir Taha 2012-08-27 03:07:48 UTC

I am using ubuntu quantal with  KDE 4.9 and Kopete 1.3 and I couldn't connect. What information can do you need? This is what I get:

$ kopete
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 16: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/69-language-selector-ja-jp.conf", line 141: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/69-language-selector-zh-tw.conf", line 79: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 9: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 22: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 22: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 22: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 26: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 31: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 40: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf", line 11: Having multiple values in <test> isn't supported and may not works as expected
kopete(7846)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/munzir/.kde/share/apps/kabc" 
munzir@GT683R:~$ kopete(7846)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '! 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  669 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
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:  668 
Unknown signature value:  669 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
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:  668 
Unknown signature value:  669 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
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 
QMetaObject::invokeMethod: No such method HistoryPlugin::shouldExitOnClose()

Comment 7 Tristan Miller 2012-09-28 15:47:49 UTC

I'm experiencing this issue with Kopete 1.2.1 on KDE 4.8.2.  I get similar console output as  Munzir Taha Obeid.

Why is this bug still marked as NEEDSINFO and WAITINGFORINFO?  Let us know what info is required and we'll provide it.

Comment 8 Keren Sky 2012-11-07 18:01:42 UTC

I see this behavior too on up to date Kubuntu 12.10.
Cheers.

Comment 9 Pali Rohár 2013-05-21 22:55:58 UTC

Kopete in svn has updated libiris library which could fix some (SSL/TLS) connection problems. I tested Google Talk login and working fine. What is needed is to allow plain text password auth in account settings dialog.