Bug 4943 - Mysterious Universe Podcasts stopped playing after 24/04/2007 ???
: Mysterious Universe Podcasts stopped playing after 24/04/2007 ???
Status: CLOSED FIXED
Product: MySqueezebox.com
Classification: Unclassified
Component: Content
: unspecified
: PC Other
: P5 minor (vote)
: ---
Assigned To: Andy Grundman
http://podcastalley.com/PodcastAlleyT...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-26 13:07 UTC by Thomas Rosted Jensen
Modified: 2008-12-15 12:16 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Rosted Jensen 2007-04-26 13:07:40 UTC
I am using SqueezeBox3 with firmware from SlimServer 6.5.1 release.

When I try to select any of the Mysterious Universe programs through the SqueezeNetwork -> Favorites -> Podcasts,
the squeezebox just shows the "loading" animation circle.
It keeps trying to load the podcast, and doesn't react to the remote control.
Only way to stop it (after waiting up to 5 minutes) is to cut the power.

Same problem when trying to select other random podcasts...

No problems in playing other internet radio streams or using local slimserver for playing music.
My quess that this is releated to the update of SqueezeNetwork...?
Comment 1 Thomas Rosted Jensen 2007-05-01 00:31:45 UTC
Currently I am not able to recreate the problem!

There may have been a problem on the servers holding the Mysterious Universe pod casts, however I was not able to play the some of the other pod casts as well..

I have changed priority to lowest and severity to minor for now.

I will do some attempts to recreate the problem, if I can't I will change state to "WorksForMe".



Comment 2 Andy Grundman 2007-05-01 10:14:54 UTC
The reason you can't is because I fixed the bug, but forgot to update this. :)
Comment 3 James Richardson 2008-12-15 12:16:27 UTC
This bug has been fixed in the latest release of SqueezeNetwork!

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