Adium

Ticket #10382 (closed defect: duplicate)

Opened 19 months ago

Last modified 17 months ago

XMPP parse error

Reported by: fguillaume Owned by: am
Milestone: Component: Service/Jabber (XMPP)
Version: 1.2.7 Severity: normal
Keywords: Cc:
Patch Status:

Description (last modified by Robby) (diff)

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@…/Stefane Fermigier’s Computer'

Attachments

log.xml (200.0 KB) - added by fguillaume 19 months ago.

Change History

Changed 19 months ago by fguillaume

Changed 19 months ago by fguillaume

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

Changed 19 months ago by jas8522

  • pending changed from 0 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.

Changed 19 months ago by fguillaume

  • pending changed from 1 to 0

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.

Changed 19 months ago by Catfish_Man

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

Changed 19 months ago 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.

Changed 19 months ago by Robby

  • version set to 1.2.7
  • description modified (diff)
  • summary changed from 1.2.7 XMPP parse error to XMPP parse error

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

Changed 19 months ago by Raptor007

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

Changed 19 months ago 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.

Changed 19 months ago 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.)

Changed 19 months ago by evands

  • status changed from new to closed
  • resolution set to duplicate
  • milestone Adium X 1.3 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.

Changed 19 months ago by Robby

  • milestone set to zzzDuplicate tickets

Changed 17 months ago by Robby

  • milestone zzzDuplicate tickets deleted
Note: See TracTickets for help on using tickets.