Bugzilla – Bug 4921
SlimServer does not start: 7.0a1, build 2007-04-17
Last modified: 2008-12-18 11:12:53 UTC
System Info: Optiplex GX620, XP SP2 ENU, Steps to Reproduce: 1. On a clean ghost of XP SP2 ENU, install SlimServer 7.01, build 2007-04-17. 2. Afster the installaltion, start slimServer. 3. After 5 minutes, mouse over the SlimTray. 4. Notice the tooltips still says "SlimServer starting". 5. Right click SlimTray. Notice almost none of the menu items is enabled. Note: Tried on another PC with Vista. SlimServer would not start either.
Wallace - can you retest with the latest 7.0 build?
Please, if you are going to set a report as a bock, please be prepared to follow up on it more quickly than this. Technically, all other development has to stop due to a blocker. Instead, this just dilutes the real meaning of priorities and severities.
Sorry, Wallace is having some kind of work done on his house. This is what shows up in the event log when I try to run last night's nightly. Event Type: Error Event Source: Application Event Category: None Event ID: 0 Date: 4/20/2007 Time: 10:33:41 AM User: N/A Computer: XPLOADED-ORIG Description: The description for Event ID ( 0 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Can't use string ("audiodir = C:\Documents and Sett") as a HASH ref while "strict refs" in use at /PerlApp/Slim/Utils/Prefs/OldPrefs.pm line 38. .
Chris/Wallace - I think this specific issue should be fixed. Does it work for you now?
Wallace, I seem to see your automated test results for 7.0 this morning. Does that mean this issue is fixed?
Hi, Chris, Yes, 7.0a1 started just fine with automated tests this morning. I am verifying the fix manually right now. If all work out, I will close this as fixed and verified. Thanks Wallace
Verified the fix using build 2007-04-23 of 7.0a1 on both Vista and XP SP2, both automatically and manually. Bug as written is no longer seen. Marking as VERIFIED.
Closing.