Export to GitHub

pidgin-musictracker - issue #198

wrong id3 tag in audacious 1.5.1 call in pidgin xml-parse error and disabling account


Posted on Feb 9, 2010 by Swift Rabbit

What steps will reproduce the problem? 1. load in audacious mp3 with id3 tag with cp1251 charset 2. click play

What is the expected output? What do you see instead?

pidgin say parse error

What version of musictracker are you using? What version of pidgin are you using? On what operating system?

ubuntu 9.04 musictracker 0.4.13 Pidgin 2.6.5

What media player are you using? audacious 1.5.1

What IM protocol(s) are you using? XMMP

Please attach or paste output from pidgin's Help/Debug Window (be careful to remove any protocol usernames you don't want made public)

<artist>Áåñïðèçîðíèêè</artist><title>Èáðàãèì</title>

(11:24:50) jabber: XML parser error for JabberStream 0xa838cc8: Domain 1, code 9, level 3: xmlParseCharRef: invalid xmlChar value 18 (11:24:50) jabber: xmlParseChunk returned fatal 9

Please provide any additional information below. Please ensure that the " Notify me of issue changes" star is switched on, so you get email when this issue is updated.

Comment #1

Posted on Mar 1, 2010 by Swift Hippo

Thanks for the reproduction steps. For some reason this only seems to reproduce with jabber.org, and not with googlemail.com jabber server, which I tried first :S

(20:19:17) jabber: Recv (ssl)(430): Audacious: Ôèäåëü by Áåñïðèçîðíèêè on ?>?KE0E (3:37) [blah blah blah]1http://jabber.org/protocol/caps' node='http://pidgin.im/' hash='sha-1' ver='AcN1/PEN8nq7AHD+9jpxMV4U6YM=' ext='voice-v1 camera-v1 video-v1'/> (20:19:17) jabber: XML parser error for JabberStream 0x9c0f450: Domain 1, code 9, level 3: xmlParseCharRef: invalid xmlChar value 18 (20:19:17) jabber: xmlParseChunk returned fatal 9 (20:19:17) connection: Connection error on 0x9c0f678 (reason: 0 description: XML Parse error) (20:19:17) jabber: Recv (ssl)(112): (20:19:17) jabber: xmlParseChunk returned fatal 9 (20:19:17) account: Disconnecting account jon.turney@jabber.org/ (0x9b9ec80) (20:19:17) connection: Disconnecting connection 0x9c0f678

Comment #2

Posted on Mar 2, 2010 by Swift Hippo

The problem seems to be that the album title for that MP3 contains a 0x12 character, which is not permitted as a character reference in XML.

There actually is a filter to eliminate such characters from the track information, but it's not actually enabled unless the profanity filter is enabled.

Fixed in svn r449, do printable character filtering even if profanity filter is disabled.

Comment #3

Posted on Mar 3, 2010 by Swift Hippo

(No comment was entered for this change.)

Status: FixReleased

Labels:
Type-Defect Priority-Medium Milestone-Release0.4.21