(In reply to comment #0)
> Client Version - qq2005

Try changing this to 'QQ2008'. If that works, I'll make it the libpurple default.

Thanks for the suggestion. I'll try it when I get back from work later today.

How simple it some times can be :-)
Changing 'Client Version' to qq2008 solved the problem.

Thanks a lot, so nice to have it all protocols in just one program now. I'm not sure if I'm supposed to resolve this?

Closing as NOTOURBUG. I've pinged the Pidgin list about this; see <http://pidgin.im/pipermail/devel/2009-October/008966.html> for why I didn't just change the default in libpurple.

There was a major update and at least Empathy was upgraded. I also think telepathy-haze was upgraded too.

Empathy is now 2.28.1 and telepathy-haze is 0.3.2-1. QQ client version is of course kept as qq2008.

This is shown in the log:
859821182 is now disabled
empathy/Account-FEJLFIND: 1,256217e+09: enable_or_disable_account: Account 859821182 is now enabled
empathy/Account-FEJLFIND: 1,256217e+09: _empathy_account_set_connection: Readying connection for /org/freedesktop/Telepathy/Account/haze/qq/_38598211820
empathy/Account-FEJLFIND: 1,256217e+09: emp_account_connection_cb: Signalling connection (nil) of account /org/freedesktop/Telepathy/Account/haze/qq/_38598211820
empathy/Account-FEJLFIND: 1,256217e+09: accounts_dialog_destroy_cb: 0x9d81118
empathy/Other-FEJLFIND: 1,256217e+09: user_data_destroyed_cb: user_data for 0x9e45a80 destroyed; disconnecting
empathy/Other-FEJLFIND: 1,256217e+09: user_data_destroyed_cb: user_data for 0x9e44d50 destroyed; disconnecting
empathy/Other-FEJLFIND: 1,256217e+09: user_data_destroyed_cb: user_data for 0x9e44bb0 destroyed; disconnecting
empathy/Other-FEJLFIND: 1,256217e+09: user_data_destroyed_cb: user_data for 0x9e43db0 destroyed; disconnecting
empathy/Other-FEJLFIND: 1,256217e+09: user_data_destroyed_cb: user_data for 0x9e44d10 destroyed; disconnecting
empathy/Other-FEJLFIND: 1,256217e+09: user_data_destroyed_cb: user_data for 0x9e44bc0 destroyed; disconnecting
empathy/Other-FEJLFIND: 1,256217e+09: user_data_destroyed_cb: user_data for 0x9e44c30 destroyed; disconnecting
empathy/Account-FEJLFIND: 1,256217e+09: _empathy_account_connection_invalidated_cb: (/org/freedesktop/Telepathy/Account/haze/qq/_38598211820) Connection invalidated
empathy/Account-FEJLFIND: 1,256217e+09: emp_account_connection_cb: Signalling connection (nil) of account /org/freedesktop/Telepathy/Account/haze/qq/_38598211820
empathy/Account-FEJLFIND: 1,256217e+09: empathy_account_connection_ready_cb: (/org/freedesktop/Telepathy/Account/haze/qq/_38598211820) Connection failed to become ready: Unknown disconnection reason
empathy/Account-FEJLFIND: 1,256217e+09: emp_account_connection_cb: Signalling connection (nil) of account /org/freedesktop/Telepathy/Account/haze/qq/_38598211820
empathy/Other-FEJLFIND: 1,256217e+09: debug_window_get_messages_cb: GetMessages failed: Method "GetMessages" with signature "" on interface "org.freedesktop.Telepathy.Debug" doesn't exist
empathy/Other-FEJLFIND: 1,256217e+09: debug_window_get_messages_cb: GetMessages failed: Method "GetMessages" with signature "" on interface "org.freedesktop.Telepathy.Debug" doesn't exist

Please get debugging output from Haze as per <http://telepathy.freedesktop.org/wiki/Debugging>.

Think maybe problem is caused by new security test started by QQ one of these days?
This morning when I would logon to QQ on my XP I got a security warning where and answering some questions on a page was required. On my Ubuntu I didn't see this security warning, but as I now have passed it on XP it will might work again using Empathty.

Anyway I'll test it later today and report back how it goes. If not I'll of course use the page you mentions for debugging.

Looks like it was the security warning causing the problem so no problem to login at all :-)

Thanks a lot for your time. I've selected the same closure code (Closing as NOTOURBUG) as you used earlier.

(In reply to comment #8)
> Looks like it was the security warning causing the problem so no problem to
> login at all :-)

FWIW, in reply to my mail to the Pidgin list about this, khc warned of exactly this kind of problem with QQ2008: <http://pidgin.im/pipermail/devel/2009-October/008973.html>.