Adium

Opened 7 years ago

Last modified 7 years ago

#16037 new defect

Adium is appending the character  to the custom status message "@ the office" and this is braking the XML.

Reported by: yferrer Owned by:
Milestone: Component: Adium Core
Version: 1.5.1 Severity: normal
Keywords: Cc:
Patch Status:

Description (last modified by wixardy)

Summary

This is happening using the Jabber Openfire Server. Once I'm connected if I change my custom message to "@ the office" the client literally sends to the server: <status>&#x10;@ the office</status>. Everyone connected gets my status and bad things start to happen. None of the clients can parse the character &#x10; and all the clients fail until I change my status to something else.

Steps to reproduce

  1. Connect to a Jabber Openfire Server using Audium 1.5.1
  2. Set the custom message: "@ the office" (without the quotes)
  3. Wait.

Expected results

I expected to not send this weird character and just set "@ the office" as my custom message.

Actual results

The Adium client sends my presence status like this:

<presence><status>&#x10;@ the office</status><c xmlns='http://jabber.org/protocol/caps' node='http://pidgin.im/' hash='sha-1' ver='DdnydQG7RGhP9E3k9Sf+b+bF0zo='/><x xmlns='vcard-temp:x:update'><photo/></x></presence> 

Regression

This bug was found in: OSX 10.7.4 Lastest Adium version: 1.5.1 Occurs all the time.

Logs

17:04:54: <ESPurpleJabberAccount:8c1fb50 5>:my@email.com: privacyOptions are 1
17:04:54: Setting status on 8cf4a00 (my@email.com/xs-MacBook-Air): ID available, isActive 1, attributes {
    buzz = 1;
    message = "<FONT>@ the office</FONT>";
    priority = 0;
}
17:04:54: (Libpurple: jabber) Sending (ssl) (my@email.com/xs-MacBook-Air): <presence><status>&#x10;@ the office</status><c xmlns='http://jabber.org/protocol/caps' node='http://pidgin.im/' hash='sha-1' ver='DdnydQG7RGhP9E3k9Sf+b+bF0zo='/><x xmlns='vcard-temp:x:update'><photo/></x></presence>

Change History (1)

comment:1 Changed 7 years ago by wixardy

  • Description modified (diff)
Note: See TracTickets for help on using tickets.