[Pidgin] #582: libpurple doesn't publish ICQ away messages

[Pidgin]

#582: libpurple doesn't publish ICQ away messages
------------------------+---------------------------------------------------
 Reporter:  metalzelot  |        Owner:  MarkDoliner
     Type:  defect      |       Status:  new        
Milestone:              |    Component:  ICQ        
  Version:  2.0         |   Resolution:             
 Keywords:              |  
------------------------+---------------------------------------------------

Comment(by Steltie):

 I can confirm that bug, it's still present in 2.5.2 (Windows and Linux).

 When I set a status message, it is sent to the ICQ server and will also be
 displayed in the buddy list (I tried that with a second ICQ account), but
 only a few seconds. Then it automatically changes to "Away".
 I noticed that the status message is displayed correctly in the AIM-Info,
 though.

 I tried to find that bug in the source, but without much success. ^^ I
 inserted some debug messages here and there and I noticed that the message
 is sent to the server as it should be, but after a few seconds, when the
 status message disappears, ... nothing is sent to the server (so it's not
 an accidental "delete away message"-command sent).

 Here are my debug messages... if you can actually use them.

 (23:16:55) oscar: Set status to away
 (23:16:55) oscar: setextrainfo(): seticqstatus = true, icqstatus = 131073,
 setavailmsg = false
 (23:16:55) oscar: tlv add raw: type 6, len 4, value -1079144288
 (23:16:55) oscar: in aim_locate_setprofile: awaymsg = 'test', away
 encoding = 'us-ascii'
 (23:16:55) oscar: tlv add raw: type 3, len 31, value 135517560
 (23:16:55) oscar: tlv add raw: type 4, len 4, value 137678080
 (23:16:55) oscar: setextrainfo(): seticqstatus = true, icqstatus = 131073,
 setavailmsg = false
 (23:16:55) oscar: tlv add raw: type 6, len 4, value -1079144160

 BTW: Available messages don't disappear, but they aren't even sent. I
 think that's a different bug, but maybe not.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/582#comment:27>
Pidgin <http://pidgin.im>
Pidgin