Bug 180325 - Jabber accounts disconnect when the Now Listening plugin sends non-ascii characters
Summary: Jabber accounts disconnect when the Now Listening plugin sends non-ascii char...
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: Now Listening Plugin (other bugs)
Version First Reported In: 0.12.7
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-11 14:13 UTC by Andres Rodriguez Guapacha
Modified: 2010-01-04 21:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andres Rodriguez Guapacha 2009-01-11 14:13:01 UTC
Version:           0.12.7 (using 3.5.10, Debian Package 4:3.5.10.dfsg.1-0lenny1 (lenny/sid))
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.26-1-amd64

With the 'Now Listening' plugin active and configured with amarok, all my jabber accounts work normally, until there are non-ascii characters (e.g. á, é, ñ and so on) in the title of the song, artist, album or anywhere in the information shown. When those characters appear, amarok continues normally, probably showing a blank square, but the moment it reaches kopete, the jabber accounts end immediatly and return a message of 'Malformed stream packet received'.
What I expected is to keep the jabber connection, even if the message shows blank squares as amarok does, but without disconnecting the account.
To reproduce I use any internet radio that tends to use those chars, or an mp3 file with ID3 tags that contain those characters; then enable the 'Now Listening' plugin to work with amarok and log in to my jabber account. Start to reproduce and the message appears.
Comment 1 Roman Jarosz 2010-01-04 21:38:44 UTC
Works in current Kopete version