Bug 449 - slimserver software won't run on new 10.3.4 OS X install
: slimserver software won't run on new 10.3.4 OS X install
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Mac Preference Pane
: unspecified
: Macintosh All
: P2 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-07-14 09:30 UTC by Chris Langford
Modified: 2008-09-15 14:37 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Langford 2004-07-14 09:30:19 UTC
I reinstalled my Mac OS X 10.3.4 system software last night, and immediately installed the slimserver 
software to run my Squeezebox.  After the installation, I clicked the start button, and the preference 
pane froze.  I reinstalled several times, for just me and for everyone on the machine, to no avail.  In 
frustration, I ran Disk Utility and repaired permissions.  This fixed the problem!  Mind you, this is on an 
absolutely clean install of 10.3.4 (Installed from 10.3.0 disks, then ran Software Update till everything 
was finished).  When I repaired permissions, only two files were fixed (see below).  The install.log file 
was repaired, and I think that's the one that was causing the problem, but I could be wrong.

Here's what was fixed when I repaired permissions:

Determining correct file permissions.
We are using special permissions for the file or directory
./System/Library/Filesystems/cd9660.fs/cd9660.util.  New permissions
are 33261
Group differs on ./private/var/log/install.log, should be 80, group is 0
Owner and group corrected on ./private/var/log/install.log
Permissions corrected on ./private/var/log/install.log
The privileges have been verified or repaired on the selected volume
Comment 1 Blackketter Dean 2004-07-14 09:51:03 UTC
Hi Chris.  We haven't seen this bug before and the files that you mention aren't likely to be the issue.  
One issue we do know of is that the server will fail to start if the Home -> Library -> Logs folder is 
missing.  It may be that DiskUtility created that folder when it wrote the log out.  Could that explain the 
problem you are seeing? 

(The problem I described has been fixed in the latest nightly release...)
Comment 2 Blackketter Dean 2004-08-12 09:48:23 UTC
I believe that this has been fixed with the automatic creation of the
appropriate logs directory.
Comment 3 Chris Owens 2006-06-16 14:40:25 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.