Bugzilla – Bug 4532
Accessing player settings crashes the server
Last modified: 2009-01-29 09:47:32 UTC
Just installed Nightly 2006-11-22 on a "clean" FC5. Connected a SB1. When I then access the player settings for the SB1, the left pane reports "unable to connect" and the SB1 reports "Problem: Lost contact with SlimServer". When I then restart the server with "service slimserver start", it starts with some information: Starting SlimServer: [17:53:01.1128] SlimServer OSDetect init... [17:53:01.1140] SlimServer settings init... [17:53:01.2015] main::init (257) SlimServer OS Specific init... [17:53:01.2027] main::init (277) SlimServer daemonizing... [17:53:01.2941] Slim::bootstrap::theEND (335) Got to the END [ OK ] When the SB then connects (SB display shows something), I see this on my Terminal Window: mDNSResponderPosix: Responder.c:562: RegistrationCallback: Assertion `&cursor->coreServ != thisRegistration' failed.
Created attachment 1722 [details] Log-file from the test This is a log-file from my test. Started the server, waited for the SB to connect, and then pressed Player Settings.
please note: http://forums.slimdevices.com/showthread.php?t=29218&highlight=trunk+unstable this is basically harmless, but as there is much more code restructuring to come, we would appreciate not having a flood of low level bug reports like this about 7.0 (trunk) thanks.
for now, add use Slim::Utils::Strings; at the top of Slim/Web/Settings/Player/Basic.pm
fixed by Dan at change 10748