Bug 9576 - Setup does not start after a factory reset
: Setup does not start after a factory reset
Status: CLOSED FIXED
Product: SB Controller
Classification: Unclassified
Component: Setup
: unspecified
: PC Windows XP
: -- critical (vote)
: 7.3
Assigned To: Ben Klaas
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-24 11:44 UTC by Richard Titmuss
Modified: 2008-12-15 12:40 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Titmuss 2008-09-24 11:44:27 UTC
 
Comment 1 Ben Klaas 2008-09-25 09:11:08 UTC
I believe that r2970 should fix this issue. Marking as fixed-- I will verify with new build.
Comment 2 Ben Klaas 2008-09-25 12:51:08 UTC
Not fixed with r2970. Reopening.
Comment 3 Ben Klaas 2008-09-25 12:59:41 UTC
adding Tom...Tom, this feels kind of similar to what we're seeing in desktop squeezeplay--that the user is never guided through setup, instead seeing a home menu with "Return to Setup" in the menu.

still mine to investigate.
Comment 4 Ben Klaas 2008-09-26 12:55:42 UTC
SelectPlayer and SetupLanguage both have services called setupShow(), which is creating a conflict.

sorry, I'm heading out of town and I won't be able to fix this until Monday, but that appears to be the underlying issue...
Comment 5 Ben Klaas 2008-09-29 11:36:08 UTC
should be fixed for both desktop squeezeplay and controller in r3010

I'll verify the controller after the build is complete
Comment 6 Ben Klaas 2008-09-29 13:51:21 UTC
update: r3013 fixes another few issues later in SetupWelcome screens

verified as fixed on controller with r3013 firmware
Comment 7 Ross Levine 2008-11-20 18:59:10 UTC
Verified to be fixed in r3411.
Comment 8 James Richardson 2008-12-15 12:40:41 UTC
This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.