Adium

Ticket #10382 (closed defect: duplicate)

Opened 6 months ago

Last modified 3 months ago

XMPP parse error

Reported by: fguillaume Assigned to: am
Priority: normal Milestone:
Component: Jabber/XMPP Version: 1.2.7
Severity: normal Keywords:
Cc: Patch: None
Pending: 0

Description (Last modified by Robby)

Since 1.2.7 the connection is lost immediately at startup and the Account connection status says "XML parse error".
Attaching the XML console log, which shows a RIGHT SINGLE QUOTATION MARK (U+2019, 0xe2 0x80 0x99) in the stream for the Location in several places: from='sfermigier@jabber.nuxeo.com/Stefane Fermigier’s Computer'

Attachments

log.xml (200.0 kB) - added by fguillaume on 07/05/2008 12:51:27 PM.

Change History

07/05/2008 12:51:27 PM changed by fguillaume

  • attachment log.xml added.

07/05/2008 12:52:40 PM changed by fguillaume

(BTW the version field in Trac doesn't propose "1.2.7".)

07/06/2008 01:54:21 PM changed by jas8522

  • pending set to 1.
  • milestone set to Needs feedback from users.

Please complete all of the TroubleshootingTips and report back as to their effectiveness. Also attach a debug log as per CurrentAdiumDebug.

07/06/2008 03:01:58 PM changed by fguillaume

  • pending deleted.

Sorry, this is a production server and I can't justify rolling back to a non-working configuration to further debug. The server is Openfire 3.5.1. The problematic resource was created by iChat with a U+2019 in it. All the information I have is already attached. Fixing the resource of the one impacted user (removing the U+2019) made thing work again with Adium.

07/06/2008 03:19:36 PM changed by Catfish_Man

  • milestone changed from Needs feedback from users to Adium X 1.3.

07/07/2008 10:00:01 AM changed by fguillaume

The problem happened again. Adium 1.2.7 repeatedly logs in and out saying XML Parse error (in the Adium accounts 1-line status line). But Adium 1.3b7 works all right.

07/07/2008 11:55:51 AM changed by Robby

  • version set to 1.2.7.
  • description changed.
  • summary changed from 1.2.7 XMPP parse error to XMPP parse error.

Shouldn't this be fixed for 1.2.x, David?

07/07/2008 02:34:32 PM changed by Raptor007

I'm having the same problem here at work; we are also using an OpenFire server.

07/07/2008 02:36:46 PM changed by Catfish_Man

Update: I know what's going on, we're working to address the issue both in Openfire and in Adium. No ETA quite yet.

07/07/2008 02:42:45 PM changed by Raptor007

Contrary to what fguillaume said, I tried 1.3b7 and it has the same problem. (I will revert to 1.2.5 for now.)

07/15/2008 12:56:53 PM changed by evands

  • status changed from new to closed.
  • resolution set to duplicate.
  • milestone deleted.

This is an OpenFire bug which must be fixed serverside. See http://developer.pidgin.im/ticket/6031#comment:18 for details. Also, this is a duplicate of #10353.

07/23/2008 05:31:33 PM changed by Robby

  • milestone set to zzzDuplicate tickets.

09/26/2008 08:30:06 AM changed by Robby

  • milestone deleted.