Google talk plugin not working in kopete and kadu after libssl1.0.0 upgrade.

Bug #1022167 reported by Krystian Maculewicz
60
This bug affects 12 people
Affects Status Importance Assigned to Milestone
OpenSSL
Fix Released
High
openssl (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

After upgrading libssl1.0.0 package from 1.0.1-4ubuntu6 to 1.0.1c-3ubuntu1, google talk plugin stoped working in kopete and kadu. Downgrading to 1.0.1-4ubuntu6 fixes problem.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libssl1.0.0 1.0.1c-3ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
Uname: Linux 3.5.0-3-generic i686
ApportVersion: 2.2.5-0ubuntu2
Architecture: i386
Date: Sun Jul 8 01:00:57 2012
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
ProcEnviron:
 LANGUAGE=pl_PL
 TERM=xterm
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: openssl
UpgradeStatus: Upgraded to quantal on 2011-12-20 (200 days ago)

Revision history for this message
Krystian Maculewicz (r7g0a-spam-h6iae) wrote :
description: updated
Revision history for this message
Aditya V (kroq-gar78) wrote :

I think this might be more of a problem with Kopete and Kadu because the might not support the latest libssl. Just my thoughts...

Revision history for this message
In , Vikrant (vikrant82) wrote :

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.

Revision history for this message
In , Vikrant (vikrant82) wrote :

Any updates ?

Revision history for this message
In , Siteshwar (siteshwar) wrote :

I confirm this bug in Kopete 1.2.3

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in openssl (Ubuntu):
status: New → Confirmed
Revision history for this message
In , Vikrant (vikrant82) wrote :

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."

Revision history for this message
In , Ben Cooksley (bcooksley) wrote :

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.

Revision history for this message
In , Vikrant (vikrant82) wrote :

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

Revision history for this message
In , Munzir Taha (منذر طه) (munzirtaha) wrote :
Download full text (5.7 KiB)

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...

Read more...

Changed in openssl:
importance: Unknown → High
status: Unknown → Incomplete
Revision history for this message
vip (piotr-budny) wrote :

Any progress? It is really hard to maintain old (unaffected) libssl on amd64 with new (broken) i386 lib on 64 bit platform.

Revision history for this message
In , Psychonaut (psychonaut) wrote :

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.

Revision history for this message
Jason Straight (jason-jeetkunedomaster) wrote :

This works for me now. Since libssl 1.0.1c-3ubuntu2, just the other day.

Changed in openssl (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
In , Keren-sky (keren-sky) wrote :

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

Revision history for this message
alex kalderimis (alexkalderimis) wrote :

I know it says fix released, but I am also experiencing this issue, which only developed recently. My libssl1.1.0 is at 1.0.1c-3ubuntu2.2

(I also suspect this has broken my vpnc, but I am still investigating that...)

Revision history for this message
In , Pali (pali) wrote :

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.

Changed in openssl:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.