Pidgin cannot connect to ICQ ("The client version you are using is too old.")
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kopete |
Fix Released
|
High
|
|||
Licq |
Fix Released
|
Unknown
|
|||
Pidgin |
Fix Released
|
Unknown
|
|||
kopete (Debian) |
Fix Released
|
Unknown
|
|||
kopete (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Dapper |
Invalid
|
Undecided
|
Unassigned | ||
Feisty |
Invalid
|
Undecided
|
Unassigned | ||
Gutsy |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
pidgin (Debian) |
Fix Released
|
Unknown
|
|||
pidgin (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Dapper |
Invalid
|
Undecided
|
Unassigned | ||
Feisty |
Invalid
|
Undecided
|
Unassigned | ||
Gutsy |
Fix Released
|
High
|
Unassigned | ||
Hardy |
Fix Released
|
High
|
Unassigned |
Bug Description
On July 1, 2008, ICQ bumped the required protocol version to connect to its servers, thus breaking some third-party IM applications. This bug is for the problems in pidgin. Users affected by this bug will see the message "The client version you are using is too old. Please upgrade at http://
The bug has been fixed upstream (http://
TEST CASE: Using the old version, try to connect to any ICQ account with pidgin, and observe the above error message in the main window. With a fixed package, connecting should work fine again.
I see no potential for regression, besides ICQ changing the version string back to what it was after the fix is pushed, which is rather unlikely. Moreover, ICQ is entirely unusable for libpurple users at the minute, so there is already a severe regression from expected behaviour.
Changed in pidgin: | |
importance: | Undecided → Critical |
Changed in pidgin: | |
status: | Unknown → New |
Changed in pidgin: | |
assignee: | nobody → pidgin-developers |
Changed in pidgin: | |
assignee: | pidgin-developers → nobody |
Changed in pidgin: | |
status: | Unknown → New |
Changed in kopete: | |
status: | New → Confirmed |
Changed in kopete: | |
status: | Unknown → Confirmed |
Changed in pidgin: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in pidgin: | |
assignee: | nobody → laney |
status: | New → In Progress |
Changed in pidgin: | |
assignee: | nobody → ubuntu-bastis |
assignee: | ubuntu-bastis → nobody |
Changed in pidgin: | |
status: | Confirmed → Fix Committed |
Changed in pidgin: | |
assignee: | laney → nobody |
status: | In Progress → Confirmed |
Changed in pidgin: | |
status: | New → Invalid |
Changed in pidgin: | |
importance: | Undecided → High |
Changed in pidgin: | |
status: | New → Invalid |
Changed in kopete: | |
status: | New → Invalid |
status: | New → Invalid |
status: | New → Invalid |
Changed in pidgin: | |
status: | Confirmed → Fix Committed |
Changed in licq: | |
status: | Unknown → Fix Released |
Changed in pidgin: | |
status: | New → Fix Released |
Changed in pidgin: | |
status: | Fix Committed → Fix Released |
Changed in pidgin: | |
status: | New → Fix Released |
Changed in pidgin: | |
status: | Confirmed → Fix Committed |
Changed in kopete: | |
status: | Unknown → Fix Released |
Changed in kopete: | |
status: | Confirmed → Fix Released |
Changed in kopete: | |
importance: | Unknown → High |
tags: | added: mago |
I can confirm that bug, I have exactly the same problem.
workaround and confirmation that it is not a general ICQ problem: goto http:// go.icq. com and login there ...