Bugzilla – Bug 13455
Jive setup seem to never really register fully on SN
Last modified: 2009-10-05 14:25:37 UTC
After setup a factory reset Jive the 'Return to Setup' entry stays on for about 30 seconds than goes away automatically. Trying to access "App Gallery" results in a small spinny forever and never succeeds. To me it looks like Jive setup never really finishes. Could also be an issue on SN I guess. Steps to reproduce: - Factory reset Jive - Go through setup, i.e. select language, network, enter email and pw - Back at home menu you'll see the 'Return to Setup' which goes away eventually - Try "App Gallery" or "My Apps" Also during setup you'll find that you need to enter email / pw every time you do that, like it never really got registered on SN.
== Auto-comment from SVN commit #7285 to the jive repo by tom == == https://svn.slimdevices.com/jive?view=revision&revision=7285 == Bug:13455 +4 Description: - jive by default now has local playback off - now use jive.sn - setup: sn reg happens before player selection - receiver setup auto-selects SN
== Auto-comment from SVN commit #7301 to the jive repo by tom == == https://svn.slimdevices.com/jive?view=revision&revision=7301 == Bug:13455 +4 Description: - have baby and fab4 setups go home after serverLinked now that the slimbrowse code doesn't go home directly in a slib borwse serverLined case. - Refactor all three machines (fab4, baby, jive), setup use copy of same end flow (step 9 to clean up and go home.)
resolved now that jive setup is "no local player" only.
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.