Adium

Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#6533 closed defect (fixed)

“Unable to format screen name” error on ICQ

Reported by: boredzo Owned by: nobody
Milestone: Adium X 1.1 Component: Service/ICQ
Version: Severity: normal
Keywords: icq error message connect Cc:
Patch Status:

Description

When I connect my ICQ account, I get this message:

Error Changing Account Info

Error 0x0006: Unable to format screen name because it is invalid.

It doesn't mention what service nor what account, and I don't know what it's trying to do or why it's failing.

Quoth the debug log:

11:55:39: (Libgaim: status) Attempted to set status attribute 'message' for status 'Invisible', which is not legal.  Fix this!
11:55:39: (Libgaim: blist) Updating buddy status for [CENSORED] (ICQ)
11:55:39: buddy_status_changed_cb: <AIListContact:62aa540 ICQ.[CENSORED]> (4): name Invisible, message (null)
11:55:39: (Libgaim: proxy) Connected to 64.12.163.19:5190.
11:55:39: (Libgaim: oscar) connected to FLAP server of type 0x0007
11:55:39: *** info->write_tag wsa 404; now it'll be 409
11:55:40: (Libgaim: status) Attempted to set status attribute 'message' for status 'Invisible', which is not legal.  Fix this!
11:55:40: (Libgaim: blist) Updating buddy status for [CENSORED] (ICQ)
11:55:40: buddy_status_changed_cb: <AIListContact:62aa540 ICQ.[CENSORED]> (4): name Invisible, message (null)
11:55:40: (Libgaim: status) Attempted to set status attribute 'message' for status 'Invisible', which is not legal.  Fix this!
11:55:40: (Libgaim: blist) Updating buddy status for [CENSORED] (ICQ)
11:55:40: buddy_status_changed_cb: <AIListContact:62aa540 ICQ.[CENSORED]> (4): name Invisible, message (null)
11:55:40: (Libgaim: status) Attempted to set status attribute 'message' for status 'Invisible', which is not legal.  Fix this!
11:55:40: (Libgaim: blist) Updating buddy status for [CENSORED] (ICQ)
11:55:40: buddy_status_changed_cb: <AIListContact:62aa540 ICQ.[CENSORED]> (4): name Invisible, message (null)
11:55:40: (Libgaim: status) Attempted to set status attribute 'message' for status 'Invisible', which is not legal.  Fix this!
11:55:40: (Libgaim: blist) Updating buddy status for [CENSORED] (ICQ)
11:55:40: buddy_status_changed_cb: <AIListContact:62aa540 ICQ.[CENSORED]> (4): name Invisible, message (null)
11:55:40: (Libgaim: oscar) FLAP connection of type 0x0007 is now fully connected
11:55:40: (Libgaim: oscar) connected to admin
11:55:40: (Libgaim: oscar) formatting screen name
11:55:40: (Libgaim: oscar) Connecting to FLAP server 64.12.31.92:5190 of type 0x0010
11:55:40: (Libgaim: dns) DNS query for '64.12.31.92' queued
11:55:40: (Libgaim: dnsquery) IP resolved for 64.12.31.92
11:55:40: (Libgaim: proxy) Attempting connection to 64.12.31.92
11:55:40: (Libgaim: proxy) Connecting to 64.12.31.92:5190 with no proxy
11:55:40: (Libgaim: proxy) Connection in progress
11:55:40: (Libgaim: oscar) account info: because of change, perms=0x0003, err=0x0006, url=http://www.aol.com, sn=, email=(null)
11:55:40: adiumGaimNotifyMessage: type: 0

Error Changing Account Info
Error 0x0006: Unable to format screen name because it is invalid. 
11:55:40: (Libgaim: proxy) Connected to 64.12.31.92:5190.
11:55:40: (Libgaim: oscar) connected to FLAP server of type 0x0010
11:55:40: *** info->write_tag wsa 416; now it'll be 419

Change History (4)

comment:1 Changed 13 years ago by Eric Richie

Component: NoneICQ
Milestone: Adium X 1.0.3

I'm seeing the same thing on the 1.0 branch. As he said, only happens with ICQ.

comment:2 Changed 13 years ago by Eric Richie

Milestone: Adium X 1.0.3Adium X 1.1

comment:3 Changed 13 years ago by Evan Schoenberg

Resolution: fixed
Status: newclosed

(In [19323]) Suppress notifications about screen name formatting in AIM/ICQ, as we never do this in response to a user's action so should never report success or failure. Fixes #6533

comment:4 Changed 13 years ago by Evan Schoenberg

(In [19324]) merged [19323]: Suppress notifications about screen name formatting in AIM/ICQ, as we never do this in response to a user's action so should never report success or failure. Fixes #6533

Note: See TracTickets for help on using tickets.