Bugzilla – Bug 12972
"Problem Connecting" explains a network-based error, but offers a library-based resolution
Last modified: 2009-10-05 14:37:40 UTC
I'm looking at a screen on baby that says "Problem Connecting." "Couldn't connect your Squeezebox to your wireless network. Make sure it is within range of your wireless network." The options presented are: "Try again" "Other Library" Granted, the bug was triggered when I attempted to navigate into "My Music," but how is choosing another library going to correct a network connectivity problem? I'm confused. Do we: a) know what's causing this bug? (I think I filed this a while back, then it got resolved because we hadn't seen it in a while). b) know what we REALLY want the user to do to try and resolve it? Either the error message is wrong or the suggested way of fixing it is wrong.
After discussing with Ben, the available options are correct, but the title and supporting text are incorrect. Title of screen should read: "Can't Connect to Library" Copy: "We couldn't connect to [servername]. If this problem persists, please check Squeezebox Server to make sure it is running properly, and that you have a strong network connection." Options: "Try again" "Choose Different Library" (Note for QA: I added the second sentence as a guess - I have no idea what actually causes this error to occur. Am willing to change text if we can better target what triggers this bug).
strings checked in, r6751 changed "strong network connection" to "reliable network connection"
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.