Bugzilla – Bug 16692
Slacker - Playing one song and then stopping
Last modified: 2012-04-27 05:33:25 UTC
This has been reported by multiple customers, slacker will play a single song and then stop. Often you can click FWD to skip, but it skips 2 songs, buffers, and plays one more song before stopping again. It has even froze a Radio until unplugged.
See also 16693
I have been having this problem for probably 3-4 months. When I play a slacker station, it often buffers and freezes saying "buffering 5%". Sometimes it will just freeze up all-together and other times it will play the next song. Often, it will only play 1-3 songs before it stops again. Sometimes when it freezes at the end of a song, the sb reads "connection reset by remote" and stops playing. I am not using any remote. This happens on both wired and wireless connections. When I am wireless, my sb says I have about a 95% connection. I am using 10 meg internet connections and I tested this with Logitech support (I did what they said and followed some steps at home) and they said it was a really good connection. I am running Squeezebox firmware 7.5.2.
Similar problem using my Squeezebox Duet. Have tried on 3 separate networks, both wired and wireless with same results. Songs will play for 10-20 seconds, then skip to the next song and repeat. Other times it will start and stop playing and read "buffering 5%" on the screen below the song title. Had similar results using rhapsody's app as well.
Yeah, I achieved the same results using the squeezebox server on my PC. Don’t have a Mac, so I can’t confirm if that is a problem. I have also hooked it up to my modem with absolutely no firewalls on, and nothing changed
My radio and Touch are usiing FW 7.7.1-r9557. Slacker will sometimes just stop at the end of a tune. Even stranger. On other occasions, after I have put the divice into standby from Slacker, it will just will just turn itself back on and start playing without any human command. This is usually some considerable (hours) later.
*** Bug 16092 has been marked as a duplicate of this bug. ***
*** Bug 17941 has been marked as a duplicate of this bug. ***
*** This bug has been confirmed by popular vote. ***