Bug 6080 - SC7.0a1 settings not detected
: SC7.0a1 settings not detected
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Setup
: 7.0
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-06 17:29 UTC by Philip Meyer
Modified: 2007-11-14 14:00 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2007-11-06 17:29:41 UTC
I have been running 7.0a1 for a while now, but after upgrading to SVN 14436 I had an empty music library.

I identified the problem by analysing the filesystem file requests, which indicated that SqueezeCenter was now only looking for the settings within All Users Application Data.

Previously, settings were stored within the .\server\prefs folder.

As the settings were not found, a new prefs folder is created within C:\Documents and Settings\All Users\Application Data\SqueezeCenter.

Using the default settings that get created, SqueezeCenter then starts scanning for music.  It finds that I have an iTunes library and starts to import songs from that, which is so not what I want it to do, as I normally disable iTunes.

I think that as part of trying to find settings, it should look for .\server\prefs.

I think that if the first startup after installation doesn't find any settings, SqueezeCenter should not assume anything until the user makes some decisions within the setup wizard in the WebUI.

Only then should it start a full music scan.
Comment 1 KDF 2007-11-06 17:38:23 UTC
http://svn.slimdevices.com/?rev=14413&view=rev (most important part of the note...SC6-7 migration ONLY)
Comment 2 Philip Meyer 2007-11-06 17:53:34 UTC
Ah, thanks - I didn't look back through SVN log messages far enough or closely enough after I did my SVN update.

I run the server from the source code as a service via srvany.exe and ActivePerl.  I don't therefore run any installer, but I guess the "OSDetect" part of that change still affected me.

I think it is bad to assume settings and start scanning before there is any user interaction, although perhaps this is just because I don't need to run any installer package?  Maybe there is something in there that creates/migrates the settings as per some user choices?
Comment 3 KDF 2007-11-06 19:36:47 UTC
there is a report for postponing scanning until the wizard is completed: bug 5552
Comment 4 Michael Herger 2007-11-13 08:06:31 UTC
Phil - can this be considered fixed with change 14663?
Comment 5 Philip Meyer 2007-11-14 14:00:08 UTC
Yes, change 14633 should cover this bug.