Bugzilla – Bug 7787
New players don't always get a name
Last modified: 2009-07-31 10:19:26 UTC
I am no longer able to successfully connect duet using the bridged configuration with the nightlies. Ray will connect to the sever but jive will always timeout. I believe this is a server issue and not firmware. To reproduce: 1 Connect a ray to your network via Ethernet and factory reset both the ray and jive. 2 Choose your ray for wireless connection. 3 Choose your music source. 4 Notice how ray will connect but jive will timeout. I have tried with a number of different fw combinations including ray fw 22 and jive 2097. It even works fine for me with SC 7.0 using the latest ray and jive fw.
Created attachment 3216 [details] Jive log failing to connect bridged Jive log of failed bridged connection with ray fw 23 and jive fw 2097 and sc 7.0.1 18576
Hmm, but this stands out: Jan 1 00:01:31 (none) user.info jive: (NetworkThread.lua:246) - NOTIFY playerNew: Player {SS SB3 06:1f:58} Jan 1 00:01:31 (none) user.err jive: (RequestHttp.lua:67) - Response sink:/usr/share/jive/jive/slim/Player.lua:493: attempt to concatenate field 'name' (a function value) stack traceback: /usr/share/jive/jive/utils/coxpcall.lua:28: in function </usr/share/jive/jive Maybe related to the new default player name code? Ben, any ideas?
That may be the problem, I had a player the other day with a (nil) name. I am not sure how or why the player got that name. This didn't work well on the web interface, and caused Jive not to see the player. I added a work around in Jive, but probably not during setup.
I tested using an SC that had already known about the Ray and it worked fine. Removed that player from the prefs file and it failed, however the name was sent over as "Squeezebox".
Tried again while watching on the serial console and couldn't reproduce the problem. :( The name should never be nil I don't think. Assigning back to QA.
Steven to assign to Alan after figuring out how to repro.
I installed the latest nightly and I am no longer able to reproduce either. I am going resolve this as works for me. I will keep an eye out for this behavior and will reopen of I see it again.
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
Reduce number of active targets for SC