Bug 133806 - Invalid character in id3 makes current playlist not to load completely
Summary: Invalid character in id3 makes current playlist not to load completely
Status: RESOLVED DUPLICATE of bug 133793
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-09 13:51 UTC by Johnny Fu
Modified: 2006-09-09 14:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Johnny Fu 2006-09-09 13:51:01 UTC 
Version:           1.4.1 (using KDE 3.5.4, Debian Package 4:3.5.4-3 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.16.16-kanotix-1

When starting amarok an error pops up and the playlist is quite incomplete in comparison to when closing amarok. I found it in a log file
.kde/share/apps/amarok/statusbar.log.1:

"[09.09.2006 02:12] Das XML in der Wiedergabeliste ist ungültig. Bitte berichten Sie diesen Fehler an
die Amarok-Entwickler. Danke."
(Translation: the xml of the playlist is not valid. please report to developers)


This bug appears only when option to load playlist at startup of amarok (current.xml) is active and there's some invalid character within the id3 Tag.

For my case there appeared the following error output to commandline when closing amarok:

"QDom: saving invalid character , the document will not be well-formed
QDom: saving invalid character , the document will not be well-formed"

These two errors belong to the comments section of two songs - I removed the characters from the id3 tag within amarok and saved it back to mp3, then the errors disappeared.


Amarok should ignore these characters to guarantee well-formed xml - or correct it when loading the current.xml / when updating media library.
Comment 1 Johnny Fu 2006-09-09 13:56:46 UTC 
There's a similar bug http://bugs.kde.org/show_bug.cgi?id=79436
But it's two years old and already resolved...
Comment 2 Seb Ruiz 2006-09-09 14:21:40 UTC 

*** This bug has been marked as a duplicate of 133793 ***