Launchpad has imported 25 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=554923.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2010-01-13T02:17:49+00:00 Sean wrote: This is filed against Empathy 2.28.2. After performing a system update, Empathy is unable to login to AIM and ICQ. Interestingly, Pidgin is also experiencing the same error, reporting the problem as "Received unexpected response from https://api.screenname.aol.com/auth/clientLogin";. Empathy didn't specify what the problem was. On the basis of that error, I ran Wireshark and watched the login attempt. Empathy sends the following request to the server (with personal details omitted): ---------- GET http://api.oscar.aol.com/aim/startOSCARSession?a=[...]&f=xml&k=[...]&ts=1263348414&useTLS=1&sig_sha256=[...] HTTP/1.0 Connection: close Accept: */* Host: api.oscar.aol.com ---------- The response from the server is then as follows: ---------- HTTP/1.1 200 OK Date: Wed, 13 Jan 2010 02:06:54 GMT Server: Apache Content-Length: 286 Pragma: no-cache Cache-Control: no-store,no-cache,must-revalidate Keep-Alive: timeout=1, max=61 Connection: Keep-Alive Content-Type: text/xml <?xml version="1.0" encoding="UTF-8"?> <response xmlns="http://developer.aim.com/xsd/aim.xsd";><statusCode>400</statusCode><statusText>useTLS=1 is not allowed for non secure requests.</statusText><data><ts>1263348414</ts><upgradeData></upgradeData><betaData></betaData></data></response> ---------- Empathy then reports that the login failed. I have verified that my accounts are still valid: they successfully connect using the website Meebo. It is interesting that both Empathy and Pidgin are suddenly experiencing the same error. Thinking that the bug must be on AOL's side, I checked with other (non-Fedora) Empathy/Pidgin users, but haven't been able to find anyone else who could reproduce the bug. The output of `rpm -ql --last` | head -75` is provided in the attachment. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/2 ------------------------------------------------------------------------ On 2010-01-13T02:18:35+00:00 Sean wrote: Created attachment 383392 rpm -ql --last | head -75 Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/3 ------------------------------------------------------------------------ On 2010-01-14T14:33:23+00:00 Christopher wrote: I am experiencing the same error (confirmed with Wireshark) in Empathy after updating from libpurple-2.6.4-2.fc12.i686 to 2.6.5-1.fc12.i686. I undid a batch of updates applied at 2010-01-13 12:54, which brought me back to libpurple-2.6.3-2.fc12.i686. After rebooting, I was able to connect to the AIM network in Empathy. Then I updated Empathy only, to 2.6.5-1.fc12.i686, and I started getting the same error again. libpurple is part of the pidgin component, but I don't know whether the problem is in Empathy or libpurple code. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/16 ------------------------------------------------------------------------ On 2010-01-14T15:06:10+00:00 Christopher wrote: According to Bug 554978, Pidgin upstream is working on a fix. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/18 ------------------------------------------------------------------------ On 2010-01-16T02:45:21+00:00 Sean wrote: This bug is closed by empathy-2.28.2-2.fc12, which is currently in updates-testing. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/20 ------------------------------------------------------------------------ On 2010-01-16T17:54:20+00:00 Christopher wrote: Fix confirmed. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/21 ------------------------------------------------------------------------ On 2010-02-10T16:06:48+00:00 Jonathan wrote: I've got empathy-2.8.2-2.fc12.x86_64, and I am still having this problem this morning. Pidgin wasn't working for me either, but I was able to get it to work by disabling clientlogon in the advanced settings. I can't find that setting anywhere in empathy, so I believe this is still an issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/23 ------------------------------------------------------------------------ On 2010-02-10T22:00:35+00:00 Reinhard wrote: I can confirm Jonathans statement for empathy-2.8.2-2.fc12.x86_64. I receive "network connection error" for AIM as stated and for ICQ and IRC that were working before. Jabber (Googlemail) amd YIM are working still fine. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/24 ------------------------------------------------------------------------ On 2010-02-11T15:25:06+00:00 Benjamin wrote: I still see this problem with empathy-2.8.2-2.fc12.x86_64 and libpurple-2.6.5-1.fc12.x86_64. Tracing the connection, I see the same TLS error as Sean. It appears that the site api.oscar.aol.com is listening on port 443 as well as port 80. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/25 ------------------------------------------------------------------------ On 2010-02-14T01:34:43+00:00 Christopher wrote: There was an outage for a few hours for me, but everything's working fine now. Are others still experiencing this problem? Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/26 ------------------------------------------------------------------------ On 2010-02-14T09:06:44+00:00 Reinhard wrote: AIM, ICQ, Jabber and Yahoo are fine now for me (same sw as described above). Only IRC still breaks. Maybe a user settings issue; will have to verify Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/27 ------------------------------------------------------------------------ On 2010-02-14T18:04:23+00:00 Christopher wrote: Tentatively closing again... Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/28 ------------------------------------------------------------------------ On 2010-02-15T02:13:11+00:00 Jonathan wrote: Empathy is working for me again, but I don't think this means that the bug has been resolved, so I am reopening the ticket to make sure that my comment is addressed. I'm perfectly fine if you disagree with me and they way you "address" my comment is by closing the ticket again; I just want to make sure that the issues I am raising here are known to the maintainer of the package. When empathy was failing on Fedora 12, the official AIM was working fine on Windows, and pidgin worked when I disabled clientlogin. Now, while it may be true that AOL did something to their servers to make empathy start working again, if there is a time during which other clients work and empathy didn't, then that strikes me as a bug in empathy, regardless of whether that time passed. It has happened several times now, and I assume will continue to happen in the future, so whatever the problem with the servers is, empathy needs to be fixed to cope with it. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/29 ------------------------------------------------------------------------ On 2010-02-21T20:29:11+00:00 nayfield wrote: I am having this problem now, the first time I am using empathy. Wireshark confirms that it is the same message from aol as in the description. The issue seems that empathy is connecting to api.oscar.aol.com on port 80 (non encrypted) and providing the startOSCARsession request including useTLS=1. I would expect that connecting to 443 and giving the exact same request would work just fine, or connecting to 80 and not asking for useTLS=1. AOL is effectively saying that if you want to have a secure (useTLS=1) connection, you should use https (443) to start it, or you're exposing a bunch of stuff (the startOSCARsession parameters which can probably be decoded pretty easily). Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/32 ------------------------------------------------------------------------ On 2010-02-21T21:17:13+00:00 nayfield wrote: Confirmed that applying this upstream patch fixes the issue. Note, it must be applied to the pidgin SRPM since it applies to libpurple. I can't reassign the component of this bugzilla. http://developer.pidgin.im/viewmtn/revision/diff/267f28808ab6eeda6b5d68f6433f2b3fcf230d4f/with/0e3079d15adeb12c1e57ceaf5bf037f9b71c8abd/libpurple/protocols/oscar/clientlogin.c Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/33 ------------------------------------------------------------------------ On 2010-02-21T21:17:47+00:00 nayfield wrote: Created attachment 395391 Patch against pidgin SRPM Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/34 ------------------------------------------------------------------------ On 2010-02-21T22:13:04+00:00 nayfield wrote: thanks for the reassign brian. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/35 ------------------------------------------------------------------------ On 2010-02-22T17:13:54+00:00 Warren wrote: AOL changed their server for the previous clientLogin issue more than once within a week. Upstream is not yet sure that this is the only issue that will need to be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/36 ------------------------------------------------------------------------ On 2010-03-04T21:16:15+00:00 Fedora wrote: pidgin-2.6.6-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/pidgin-2.6.6-2.fc12 Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/37 ------------------------------------------------------------------------ On 2010-03-04T21:16:21+00:00 Fedora wrote: pidgin-2.6.6-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/pidgin-2.6.6-2.fc13 Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/38 ------------------------------------------------------------------------ On 2010-03-04T21:16:28+00:00 Fedora wrote: pidgin-2.6.6-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/pidgin-2.6.6-2.fc11 Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/39 ------------------------------------------------------------------------ On 2010-03-05T03:36:40+00:00 Fedora wrote: pidgin-2.6.6-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/40 ------------------------------------------------------------------------ On 2010-03-09T08:28:38+00:00 Michal wrote: *** Bug 563812 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/41 ------------------------------------------------------------------------ On 2010-03-10T06:43:55+00:00 Fedora wrote: pidgin-2.6.6-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/42 ------------------------------------------------------------------------ On 2010-03-10T06:55:38+00:00 Fedora wrote: pidgin-2.6.6-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/43 ** Changed in: empathy (Fedora) Status: Unknown => Fix Released ** Changed in: empathy (Fedora) Importance: Unknown => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/506647 Title: Can't login to ICQ or AIM servers "Received unexpected response from http://api.oscar.aol.com/aim/startOSCARSession"; Status in Empathy: Invalid Status in empathy package in Ubuntu: Invalid Status in pidgin package in Ubuntu: Fix Released Status in pidgin package in Debian: New Status in empathy package in Fedora: Fix Released Status in pidgin package in Fedora: Invalid Bug description: Binary package hint: pidgin After an Pigdin crash i couldn't re-login with my ICQ Account, i didn't changed anything at the Programm Failure msg. "Unexpectet Answer from* http://api.oscar.aol.com/aim/startOSCARSession"; (*Translation from German sry for gramma fails). OS: Ubuntu 9.04 ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/pidgin NonfreeKernelModules: nvidia Package: pidgin 1:2.6.5-0ubuntu1~pidgin2.9.04 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.28-17-generic i686 UnreportableReason: Das Paket stammt nicht von Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/506647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
