Bugzilla – Bug 12039
"Problem Connecting" to wireless network when trying to connect to mysqueezebox.com or a local SC instance
Last modified: 2009-10-06 09:21:57 UTC
- running 7.4 r533 firmware - in the office on "Squeezetest" via wifi - running SC 7.4 - 26532 AFTER successfully connecting to the "Squeezetest" network, I get the "Problem Connecting" error whenever I try to connect to mysqueezebox.com or my local SC instance. Menus, however, seem to work correctly for navigation after this (I can go into internet radio, for example, and browse stations). The moment I try to play something, the system crashes and reboots. Then I'm stuck with the same apparent connection problem...
7.4 r5733. Apologies for the typo.
How are you connecting to the wlan? Is that after a factory reset and during setup or later via the Networking menu? I tried both variants here with r5732 (and after the update from SN r5737) and didn't see an issue. Could QA please try to reproduce, thanks.
Felix, I get this error message when trying to switch server even though the fab4 is wired. I think it was related to choosing a player in the past - it seems to work again when you choose a new player and then switch back to the local player. However I think that if you set the player up as wired then it should never even scan the wireless? Why does the setting dialog ask about wireless region before asking whether to use wired or not? It should definately not show a "couldn't connect ... to your wireless network" message when its wired and you have never entered any details of the wireless network.
Thanks for the comment, QA has not been able to repo this yet, but I'll try with your suggestions of choosing a different player on the Fab4
Wouldn't you know it..right After I type in the above, I see the error without switching player source ========================== lsa_stop error in event function: ...share/jive/applets/SlimBrowser/SlimBrowserApplet.lua:1617: attempt to call local 'sink' (a nil value) stack traceback: ...share/jive/applets/SlimBrowser/SlimBrowserApplet.lua:1617: in functio n <...share/jive/applets/SlimBrowser/SlimBrowserApplet.lua:1409> (tail call): ? /usr/share/jive/jive/ui/Menu.lua:146: in function </usr/share/jive/jive/ ui/Menu.lua:141> (tail call): ? /usr/share/jive/jive/ui/Menu.lua:897: in function 'callback' /usr/share/jive/jive/ui/Widget.lua:656: in function </usr/share/jive/jiv e/ui/Widget.lua:632> [C 0x2378c]: in function 'dispatchEvent' /usr/share/jive/jive/ui/Widget.lua:532: in function 'dispatchNewEvent' /usr/share/jive/jive/ui/Menu.lua:760: in function </usr/share/jive/jive/ ui/Menu.lua:759> [C 0x52ee4]: in function 'pcall' /usr/share/jive/jive/ui/Timer.lua:187: in function '_runTimer' /usr/share/jive/jive/ui/Framework.lua:348: in function 'eventLoop' /usr/share/jive/jive/JiveMain.lua:351: in function </usr/share/jive/jive /JiveMain.lua:204> (tail call): ? /usr/share/jive/jive/JiveMain.lua:510: in main chunk [C 0x59b70]: ? [C 0x21584]: ? src/audio/decode/decode.c:473 DEBUG decode_stop src/audio/decode/decode.c:296 DEBUG handling message src/audio/decode/decode.c:164 DEBUG decode_stop_handler src/audio/decode/decode_alsa.c:659 DEBUG decode_alsa_stop src/audio/decode/decode.c:473 DEBUG decode_stop src/audio/decode/decode.c:296 DEBUG handling message src/audio/decode/decode.c:164 DEBUG decode_stop_handler src/audio/decode/decode_alsa.c:659 DEBUG decode_alsa_stop ========================
this just happened again at home. Steps taken: - perform factory reset - navigate to "my music" - choose squeezecenter instance I get the "problem connecting" screen. fab4 is about 15 feet from my router. tried connecting to "mysqueezebox.com," I get the same issue. What's weird is, after getting the error, I can navigate into "internet radio," choose a station, and play it.
Created attachment 5267 [details] Photo of error This sounds like the error I'm seeing, where Fab4 is successfully connected to my WiFi but when I try selecting a music source, it get this error. Photo attached. If I back out of this error I'm able to navigate other menus including Settings > Adv > Diagnostics where I see it's still successfully connected with 68 SNR. (wireless router is 10 feet away with no obstructions.) There are two additional bad things about this error imo: 1. At top-right you cannot get to More Help or Diagnostics. 2. The 2nd option presented is "Skip this step" which is not appropriate here.
Weird. I get the same results as Dan but my two options were "try again" nd "go back..." maybe this is a recent change from another bug?
Changing target to next major milestone (since MPQ & MP have been reached already)
I believe this has nothing to do with the wireless connection at all but with the logic of how and when Fab4 connects to SC or SN. It's also possible that Tom already fixed that issue. Reassigning to Tom to comment and possible close as fixed.
is this still happening for you?
Haven't seen it in a few weeks, actually. Closing unless/until it happens again. (It was happening a TON several weeks ago, like several times a day).
This bug has been fixed in the latest release of MySqueezebox.com (formally known as SqueezeNetwork)! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.