Bug 5468 - After rebooting I had to choose my network again.
: After rebooting I had to choose my network again.
Status: CLOSED FIXED
Product: SB Controller
Classification: Unclassified
Component: UI
: unspecified
: All All
: P2 major (vote)
: 7.0
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-09-14 12:24 UTC by Blackketter Dean
Modified: 2008-05-15 12:59 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
log from Jive that just experienced this behavior (10.54 KB, application/octet-stream)
2007-12-07 14:37 UTC, Dan Evans
Details
In case is relevant, here's another from an attempt with a wired player. This is with fw18 and r1084, upping to fw 19 and r1086. (10.79 KB, application/octet-stream)
2007-12-07 15:01 UTC, Dan Evans
Details
Log gathered from Jive connected via standard wired mode. (18.65 KB, application/octet-stream)
2007-12-10 17:32 UTC, Dan Evans
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Blackketter Dean 2007-09-14 12:24:34 UTC
I did a hard power down (press and hold the HOME button for 10 second) and when I powered back up, Jive failed to automatically reconnect to my home network (it was trying to associate with the office network instead).  Once I chose my network again, it successfully connected and went to the previously selected player.
Comment 1 Richard Titmuss 2007-09-19 07:01:09 UTC
Can you recreate this? Had you completed setup?
Comment 2 Blackketter Dean 2007-09-19 08:03:19 UTC
I had completed setup, and was controlling music when the unit locked and I rebooted.  It was trying to associate with the office network again.  This happened multiple times that day. 

Whoops, just happened again.  Make sure you have two networks saved in your settings.   (Isn't it supposed to associate with any of the networks that you've previously connected do, preferring the last one and/or the strongest one?)

Also, it did remember the encryption information and was able to associate without asking for my wep key again.

Comment 3 Richard Titmuss 2007-10-05 14:33:10 UTC
*** Bug 5570 has been marked as a duplicate of this bug. ***
Comment 4 Dan Evans 2007-10-24 14:06:03 UTC
I am still seeing this behavior after a software update today.  After the update completes I'm dumped back at the "Choose Language" screen. (per bug 5570)
Comment 5 Richard Titmuss 2007-10-30 14:39:58 UTC
Fixed in r763. Please reopen the bug if you see this again.
Comment 6 Dan Evans 2007-11-06 10:08:15 UTC
This bug has returned.

I updated to r821 (Nov 6) and after the software update completed, Jive returned to the setup sequence.  I had to enter everything again.  (not just language as before, but language, network, wireless key, etc.)
Comment 7 Richard Titmuss 2007-11-06 12:24:14 UTC
What firmware version did you have before? An upgrades since the start of last week will perform a factory reset on upgrade, when the new 2.6.22 kernel is installed for the first time.

If this is not repeatable when you upgrade the firmware next time I suggest that this bug is marked as fixed again.
Comment 8 Dan Evans 2007-11-06 12:38:20 UTC
I updated yesterday, so I had whatever firmware was available in Monday night's build. 
Comment 9 Richard Titmuss 2007-11-07 09:02:48 UTC
I have not seen this problem today, after many upgrades. I need a repeatable test case to be able to investigate this further.
Comment 10 Richard Titmuss 2007-11-09 02:56:34 UTC
It's worth noting that until you get to the "setup complete" screen you will have to complete the setup screens on each boot, so if you use the the home key to quit setup early then you will be prompted to setup again on the next boot. This is related to bug 5282.
Comment 11 Dan Evans 2007-12-07 12:37:09 UTC
This is showing up today with the MP firmware, r1084.  We've seen this on multiple Jives during testing so far.

We're using :

* SqueezeCenter v7.0 - 15077 
* Jives installed with r1084, that are then upgraded to r1086
* Rays on fw 18

* a Linksys WRT54G router with WPA2 encryption
Comment 12 Richard Titmuss 2007-12-07 13:30:11 UTC
ok i don't see this here. please use an SD card to get the log information from jive so i can have a look. cheers.
Comment 13 Dan Evans 2007-12-07 14:37:15 UTC
Created attachment 2483 [details]
log from Jive that just experienced this behavior
Comment 14 Dan Evans 2007-12-07 15:01:23 UTC
Created attachment 2484 [details]
In case is relevant, here's another from an attempt with a wired player.  This is with fw18 and r1084, upping to fw 19 and r1086.
Comment 15 Dan Evans 2007-12-07 15:04:44 UTC
Sorry, just to clarify:  both logs are from controller/player with fw 18 and r1084 and upgraded to fw 19 and r1086.
Comment 16 Blackketter Dean 2007-12-07 16:21:23 UTC
We need this fixed before MP.
Comment 17 Richard Titmuss 2007-12-10 05:29:34 UTC
Thanks Dan, the log was useful to help my understand what the problem was. I misunderstood the steps to recreate, after reading the log it all became clear.

Fixed in r1101.
Comment 18 Dan Evans 2007-12-10 17:31:24 UTC
Richard,

I had thought this was fixed, but I may have spoken too soon.  

When testing both Jive&Ray connecting wirelessly, this bug is gone.  But while testing with Ray wired, I still see this bug.  Again, I only see this when Ray is wired.

I will attach the log I gathered.
Comment 19 Dan Evans 2007-12-10 17:32:16 UTC
Created attachment 2494 [details]
Log gathered from Jive connected via standard wired mode.
Comment 20 Richard Titmuss 2007-12-11 04:06:49 UTC
Dan, I have just tried a couple of times and I can't recreate this bug. I think Steven has also reported success with the latest firmware on a wired connection.

Looking in the attached messages file it upgrades around 16:54 then reboots at 16:55.00. According to the log after rebooting the firmware connected to the player. What I can't tell for sure (as it does not write to the log) is if the initial setup screen has been displayed. Can you recreate this?
Comment 21 Richard Titmuss 2007-12-13 09:52:23 UTC
Fixed in r1123.
Comment 22 Chris Owens 2007-12-18 16:54:51 UTC
Dan and Jim tell me to reopen this bug.  QA will attempt to verify this is really still happening.
Comment 23 Chris Owens 2007-12-18 17:49:04 UTC
It is really not still happening.
Comment 24 James Richardson 2008-05-15 12:59:29 UTC
This bug has recently been fixed in the latest release of SqueezeCenter 7.0.1

Please try that version, if you still see the error, then reopen this bug.

To download this version, please navigate to: http://www.slimdevices.com/su_downloads.html