I can confirm that the bug is somehow related to the wireless bridge settings.
Even though I was NOT and never have used the wireless bridging option, when I connected an ethernet cable and explicitly disabled wifi bridging, it solved the problem. I had the same symptoms that others have reported. I have a Squeezebox Classic, and when the problem started, I was running Squeezebox Server 7.4. (Not sure what firmware version I had.) A couple weeks ago, Rhapsody stopped working. All other apps worked fine. In Rhapsody, I could browse/search for albums/tracks, make a selection, it would say it was buffering, then act like it was playing, but no sound. I tried switching from Squeezebox Server to mysqueezebox.com, but it didn't help. I upgraded to the latest version of Squeezebox Server - v 7.6 - r32854. Reading the release notes from 7.5, and seeing there was fix for Rhapsody, I was hopeful that this would fix the problem. After the server upgrade, my Squeezebox automatically updated to firmware version 137. I tried Rhapsody - no dice. Same exact symptoms: I could connect and browse, but no music! After reading this forum, I decided to try plugging in an ethernet cable and disabling wireless bridging. Now here's the thing: I have never used wireless bridging. I have only connected my Squeezebox to my LAN wirelessly. I did not have an ethernet cable plugged in. By definition, wireless bridging is all about bridging a wireless connection with a wired one. To use it, you have to have a wired ethernet connection to some other device! Not having an ethernet cable plugged in, I did not think the comments about wireless bridging would be relevant to my setup. But I didn't know what else to try, so... I plugged in the ethernet cable, connected it to my router, held down the left arrow to re-do the network setup, chose "No" on the wireless bridge option, and after going through the rest of the setup, Rhapsody worked! I immediately disconnected the ethernet cable, and Rhapsody continues to work with no problems. So if you are only using wireless, don't worry: you don't need to keep the cable connected permanently. You just have to plug it in long enough to re-do the networking setup. Hokie, thank you so much for the tip. I will add a comment to the bug you logged. Mcoste and IceFusion, thanks for your posts. I wouldn't have expected the wifi bridging to be the problem in my case since I wasn't using it, but your posts saying that you needed to connect an ethernet cable to disable bridging convinced me to try it. -- William Szostak ------------------------------------------------------------------------ William Szostak's Profile: http://forums.slimdevices.com/member.php?userid=11160 View this thread: http://forums.slimdevices.com/showthread.php?t=88878 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
