Squeezebox Players

[Lapppi]

Just got my new Radio today. Liking it so far, except for one issue:

Whenever I attempt to access the settings for "Screen/Screensaver/when stopped" and "Screen/Screensaver/when off" (screenshot) the radio crashes and reboots after a moment. This happens wether connected to the local server, or to mysqueezebox.com.

Any idea what I could do to change the "when off" screensaver, short of using ssh? Might this be a bug in the server/firmware version I'm using? 

Logitech Media Server Version: 7.7.0 - r33614 @ Tue Oct 18 11:07:25 PDT 2011

Hostname: onyx

Server IP Address: 127.0.0.1

Server HTTP Port Number: 9000

Operating system: Debian - EN - utf8

Platform Architecture: x86_64-linux

Perl Version: 5.10.1 - x86_64-linux-gnu-thread-multi

Database Version: DBD:QLite 1.34_01 (sqlite 3.7.7.1)

Total Players Recognized: 3

Player Model: Squeezebox Radio

Firmware: 7.7.0-r9546

Player IP Address: 192.168.1.11

Player MAC Address: XXX

Wireless Signal Strength: 93%

[Lapppi]

Updated the server to the newest version available in the unstable repository, in the hope of getting an updated firmware version as well. No luck.

Now running:

Logitech Media Server Version: 7.7.1 - r33671 @ Wed Nov 9 03:03:00 PST 2011

Hostname: onyx

Server IP Address: 192.168.1.2

Server HTTP Port Number: 9000

Operating system: Debian - EN - utf8

Platform Architecture: x86_64-linux

Perl Version: 5.10.1 - x86_64-linux-gnu-thread-multi

Database Version: DBD:QLite 1.34_01 (sqlite 3.7.7.1)

Total Players Recognized: 3

[squeezeit · Accepted solution]

Working fine on my Radio, changed both Off and Stopped screensavers just fine, no reboot.

LMS 7.7 on WinXP

I can only guess your firmware update may have been corrupted or interrupted.  Maybe try connecting your Radio directly to MySB.com then force a new update.

Radio > Settings > Advanced > Networking > Connect to MySB.com

- then -

Radio > Settings > Advanced > Software Update > select update, ignore message that it will reload the same update

[Lapppi]

Thanks for the rapid response. I'm quite surprised.. that actually worked. 

I'd suggest you implement some kind of warning should an update be borked for whatever reason (perhaps using MD5 checksums).