Bug 6287 - SC7 Won't Start on OSX If SlimServer Has Ever Been Installed
: SC7 Won't Start on OSX If SlimServer Has Ever Been Installed
Status: RESOLVED DUPLICATE of bug 6001
Product: Logitech Media Server
Classification: Unclassified
Component: Mac Installer
: 7.0
: Macintosh MacOS X 10
: P2 major (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-06 19:17 UTC by ghiacabriolet
Modified: 2011-03-16 04:18 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 ghiacabriolet 2007-12-06 19:17:44 UTC
After installing SC7.0a on a Mac running OSX 10.3.9 with SlimServer v6.5.1 previously installed, SqueezeCenter won't start. The Start button changes to grey and briefly appears to be started but the server stops within a few seconds.  The console log shows the following errors:

Mac OS X Version 10.3.9 (Build 7W98)
2007-12-06 21:27:04 -0500
2007-12-06 21:33:47.241 SqueezeCenter Installer[388] LSCopyItemInfoForURL() returned -43 for path /Users/minimac/Library/PreferencePanes/SqueezeCenter.prefPane.
2007-12-06 21:33:47.242 SqueezeCenter Installer[388] LSCopyItemInfoForURL() returned -43 for path /Users/minimac/Developer/PreferencePanes/SqueezeCenter.prefPane.
2007-12-06 21:33:47.242 SqueezeCenter Installer[388] LSCopyItemInfoForURL() returned -43 for path /Library/PreferencePanes/SqueezeCenter.prefPane.
2007-12-06 21:33:47.242 SqueezeCenter Installer[388] LSCopyItemInfoForURL() returned -43 for path /Developer/PreferencePanes/SqueezeCenter.prefPane.
ERROR: Cannot find server.prefs file
ERROR: Cannot find server.prefs file
ERROR: Cannot find server.prefs file
dyld: perl can't open library: /System/Library/Perl/lib/5.8/libperl.dylib  (No such file or directory, errno = 2)
/Library/PreferencePanes/SqueezeCenter.prefPane/Contents/server/SqueezeCenter.app/Contents/Resources/start-server.sh: line 13:   474 Trace/BPT trap          ./slimserver.pl --daemon 2>&1
ERROR: Cannot find server.prefs file
dyld: perl can't open library: /System/Library/Perl/lib/5.8/libperl.dylib  (No such file or directory, errno = 2)
/Library/PreferencePanes/SqueezeCenter.prefPane/Contents/server/SqueezeCenter.app/Contents/Resources/start-server.sh: line 13:  1063 Trace/BPT trap          ./slimserver.pl --daemon 2>&1


Notes:

This problem occurs on 2 different Macs (Mac Mini and Powerbook) which had SlimServer v6.5.1 installed prior to attempting to install SC7.  The Mac Mini is a 1.25ghz PowerPC G4 with 512mb ram.  The PowerBook is an 867mhz PowerPC G4 with 640mb ram.

Additionally, the following steps did not resolve the problem:

1. Manually remove all SS files, Slim Devices files, and SqueezeCenter files and empty trash.
2. Restart computer and confirm there are no remaining Slim* or Squeeze* files on the system. Verify SS/SC do not appear in the System Preferences.
3. Run a repair of disk permissions.
4. Run a "clean" install of the 12/5 build (SqueezeCenter_trunk_v2007-12-05.dmg) and choose "All Users" (the problem also occurs if choosing only "This User"). Same symptom trying to start.

Additionally, the forum has another user reporting the same problem.  http://forums.slimdevices.com/showthread.php?t=40600

On a MacBook running 10.4.9, I was able to successfully install SC7. The MacBook never had SlimServer installed on it prior to SC7. At this point, I don't know if the difference in being able to install is due to the OS  version or the fact that SS was never on it.  

As a final note, I personally would like to see a smoother installation/upgrade process for running SS or SC on Macs.  This isn't the first time I've encountered a problem installing a newer server release on the Mac.  In the past, I had a problem installing a newer "release build" (i.e. not beta). I believe it was v6.5.5 and I ended up reverting back to 6.5.1. If this product is ever to appeal to "mainstream" users it can't have these types of problems. I've seen advice in the past where users are asked to manually track down files and delete them in order to get an installation to work and, frankly, that is pretty kludgy in my opinion. And, in cases like this where even manually removing traces of the older version doesn't fix it, that is even worse.  Otherwise, I think this is a great product.
Comment 1 Chris Owens 2007-12-10 09:15:21 UTC

*** This bug has been marked as a duplicate of 6001 ***