empathy won't connect to AIM: May be a TLS issue

Bug #526146 reported by Brian Curtis
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Invalid
Low
Unassigned
pidgin (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: pidgin

pidgin won't connect to AIM due to error Received unexpected response from http://api.oscar.aol.com/aim/startOSCARSession: useTLS=1 is not allowed for non secure requests.

i am having problems with empathy as well, and I think this may be the cause of both problems

ProblemType: Bug
Architecture: amd64
Date: Mon Feb 22 20:02:51 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
Package: pidgin 1:2.6.6-1ubuntu1
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SourcePackage: pidgin
Uname: Linux 2.6.32-14-generic x86_64
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1438): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-appearance-properties:1607): Gdk-CRITICAL **: gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed
 (gnome-appearance-properties:1607): Gdk-CRITICAL **: gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed
 (gnome-terminal:1751): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

Related branches

Revision history for this message
Brian Curtis (bcurtiswx) wrote :
Revision history for this message
Brian Curtis (bcurtiswx) wrote :

further analysis. use SSL was enabled by default in pidgin and unchecking the box for use SSL allows pidgin to work. I wonder if empathy not being able to login to AIM is because it's using SSL by default

There's no way I can see changing it in the settings provided by empathy

Pidgin job can be invalidated (and I will do so)

Changed in pidgin (Ubuntu):
status: New → Invalid
summary: - pidgin won't connect to AIM due to error Received unexpected response
- from http://api.oscar.aol.com/aim/startOSCARSession: useTLS=1 is not
- allowed for non secure requests.
+ empathy won't connect to AIM: May be a TLS issue
Changed in pidgin (Ubuntu):
importance: Undecided → Low
status: Invalid → Fix Committed
Changed in empathy (Ubuntu):
status: New → Invalid
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pidgin - 1:2.6.6-1ubuntu2

---------------
pidgin (1:2.6.6-1ubuntu2) lucid; urgency=low

  * debian/patches/90_icq_login_fix.patch:
    - upstream change to fix aim and icq login issues when clientlogin is used
      which is the case in empathy by default (lp: #524221, #526146)
 -- Sebastien Bacher <email address hidden> Wed, 24 Feb 2010 00:39:26 +0100

Changed in pidgin (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Lemmiwinks (lemmiwinks) wrote :

Hmm I guess it was not a very good idea to change that, I just updated to 1:2.6.6-1ubuntu2 which leads to a login error in icq.
Played around with a few options, like disabling clientLogin, turning on and off ssl all without any effect...

Attached my debug log.

Changed in pidgin (Ubuntu):
status: Fix Released → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

closing the bug again since the issue described there was closed, you should rather open a new bug about your new issue there

Changed in pidgin (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if it works using empathy?

Revision history for this message
Lemmiwinks (lemmiwinks) wrote :

hi there!
it works again, must have been an error with the servers...
thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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