Bug 691124 - Unable to login to ICQ account
Summary: Unable to login to ICQ account
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pidgin
Version: 6.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 6.4
Assignee: Denise Dumas
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-26 21:53 UTC by Karel Piwko
Modified: 2013-04-02 10:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-02 10:00:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Karel Piwko 2011-03-26 21:53:03 UTC 
Description of problem:

I'm unable to login to ICQ account using pidgin. I tried both original server (login.messaging.aol.com:5190) and its change to login.icq.com:5190.

I'm getting following exception:

Received unexpected response from https://api.oscar.aol.com/aim/startOSCARSession: Ok

Version-Release number of selected component (if applicable):

pidgin-2.6.6-6.el6_0.x86_64
libpurple-2.6.6-6.el6_0.x86_64

How reproducible:

Always.

Steps to Reproduce:
1. Add an ICQ account
2. Fill credentials
3. Login to the account
  
Actual results:

Login fails with an unexpected response.

Expected results:

Login succeeds.

Additional info:

Probably another ICQ protocol handling change, as usual with this protocol.
Comment 2 RHEL Program Management 2011-04-04 02:10:32 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 4 Karel Piwko 2013-04-02 10:00:07 UTC 
I'm closing this issue as WORKSFORME, as I'm not able to reproduce it anymore with RHEL 6.4 and pidgin-2.7.9-10.el6_4.1.x86_64.
Note You need to log in before you can comment on or make changes to this bug.