Bug 13945 – MP3Tunes fails to parse error message

Bug 13945 - MP3Tunes fails to parse error message

Summary:

MP3Tunes fails to parse error message

Status:	CLOSED FIXED

Product:	MySqueezebox.com
Classification:	Unclassified
Component:	SlimService
Version:	MySB
Platform:	PC Other

Importance:	P1 normal (vote)
Target Milestone:	INXS
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-10 09:12 UTC by James Richardson
Modified:	2009-10-05 16:42 UTC (History)
CC List:	1 user (show)

See Also:
Category:	Bug

Attachments
Error Image (44.42 KB, image/png) 2009-09-10 14:33 UTC, James Richardson	Details
error log (7.09 KB, application/octet-stream) 2009-09-11 09:49 UTC, James Richardson	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description James Richardson 2009-09-10 09:12:24 UTC

When playing MP3Tunes via SC 7.3.3 when connected to MySB.com, I noticed that I get a 'failed to parse' error message.

this happens when a valid MP3Tunes locker has been added to MySB.com, see attached image.

Comment 1 James Richardson 2009-09-10 14:33:28 UTC

Created attachment 5823 [details]
Error Image

Comment 2 Andy Grundman 2009-09-10 18:17:22 UTC

MP3tunes browses/plays OK for me.  If you can still reproduce, can you get a 
log with network.asynchttp and formats.xml?

Comment 3 James Richardson 2009-09-11 09:49:29 UTC

Created attachment 5831 [details]
error log

I can still repo this, see attached log.

Comment 4 Andy Grundman 2009-09-11 09:54:27 UTC

OK I see, it's something specific with your account.

Comment 5 SVN Bot 2009-09-11 12:04:58 UTC

 == Auto-comment from SVN commit #7317 to the network repo by andy ==
 == https://svn.slimdevices.com/network?view=revision&revision=7317 ==

Fixed bug 13945, fix MP3tunes handling when an account has expired

Comment 6 James Richardson 2009-10-05 16:42:22 UTC

This bug has been fixed in the latest release of MySqueezebox.com (formally known as SqueezeNetwork)!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.