Bugzilla – Bug 465
After several track skips the Squeezebox reboots when playing flac files
Last modified: 2009-01-14 10:13:17 UTC
At least in firmware 31. I have not had the time to trace back. Also note that it could alse be the software but I have reported it as firmware since it causes a Squeezebox reboot. When skipping ahead through a playlist (ie. listening for a bit then going to the next track) after about 4-10 skips or forwards the Squeezebox will reboot. Sometimes it is preceeded by some unresponsiveness or frozen display. I have tried it with the handfull of MP3s I have and the reboot does not seem to happen.
Is this player wired or wireless? If wireless, is it currently wired to the network? If it's a wireless player currently being used wired, could you try taking out the wireless card in the unit and see if it stops doing this?
It is wireless and I am currently *not* using the wireless connection but rather have it directly connected via Cat5. I don't have time at the moment to pull the card out but will try this when I have a chance.
Created attachment 94 [details] d_slimproto log d_slimproto log from startup of slim.exe to reboot of the Squeezebox G when fast forwarding through a playlist of FLACs.
I'm experiencing the same problem. I've attached a slim.exe log that traces d_slimproto from startup of the server process to the point at which the device reboots.
Please try the latest nightly with firmware version 32 and add your experiences. The problem appears greatly improved for me, but is still reproducable.
Firmware rev. 32 appears to have fixed the problem for me. I've been using it for two days and have not had a single reboot or issue.
Well after some testing this does seem to be fixed in 33 for me.
is it safe to mark this one fixed?
I think so. Although now I have a 'pit or pendulum' decision given that the newer firmware/slimserver has this rather nasty bug: https://bugs-archive.lyrion.org/show_bug.cgi?id=506
understandable. I'll mark this one fixed, because it basically is. going back to older firmware will, of course, bring the bug back. That's just how it works when using older firmware. The other problem will get fixed in response to the other bug report. If this problem comes back later with new firmware, it can be reopened.
Closing fixed bugs