Bugzilla – Bug 5911
RedHat: Settings Wizard: Browsing for library does not work.
Last modified: 2009-07-31 10:15:08 UTC
System Info: Dell Dimension 700cx, 679 MHz, 256 MB of RAM, RedHat, Browser is Konqueror Server Version: 7.0a1, build of 2007-10-24 Steps to Reproduce: 1. Make sure there are some songs in a folder. 2. Install the nightly. 3. SqueezeCenter starts automatically. 4. Start the browser and get to the settigns wizard. 5. On the page for users to locate their music folders, notice no folder structure shows up on the page. 6. The user needs to type in the path fo the music folder and click "Next". Even then, SC does not seem to be able to find the songs at the end of the setup. 7. Click Artists or Albums. Notice there is nothing there. Note: This bug was found by Dean. Note 2: This user is going to isntall Mozilla to see if it makes a different. Note 3: On the same PC, dual boot to XP. The same settings wizard shows the folders in hard drive, and is able to find and scan the songs.
Very likely a permissions issue. If it doesn't even accept the manually entered path it can't read it.
I've installed on RH dozens of times over the last few days and have never had this problem (using firefox). Is this installed from the RPM or tarball?
I'm just in the process of setting up a new CentOS 4.4 based machine. I installed the RPM and it wouldn't even start, due to permissions issues: it created Cache, Logs, prefs in /usr/local/slimserver, but as these were owned by root, it lacked permission to write there. Thus it faild starting. In fact I wondered whether the latest RPM is already based on your recent changes.
Wallace - whenever you see the web GUI only partially loaded, make sure you clean your browser's cache. In this particular case I assume SC didn't even start. What you've seen is the static content of the wizard taken from the browser's cache. And all the dynamic stuff is lacking (folder hierarchy, preference verification, saving prefs etc.). This can be very much misleading.
(In reply to comment #3) > I'm just in the process of setting up a new CentOS 4.4 based machine. I > installed the RPM and it wouldn't even start, due to permissions issues: it > created Cache, Logs, prefs in /usr/local/slimserver, but as these were owned by > root, it lacked permission to write there. Thus it faild starting. > > In fact I wondered whether the latest RPM is already based on your recent > changes. > Michael, none of my changes are in the RPMs built from nightlys - it's basically the same RPM spec that's been used for 6.5.x. The situation you describe sounds like what happens if you try to run slimserver as root instead of using "/sbin/service slimserver start" which starts it as the slimserver user.
> Michael, none of my changes are in the RPMs built from nightlys - it's > basically the same RPM spec that's been used for 6.5.x. The situation you Hmm... where are your changes then? > describe sounds like what happens if you try to run slimserver as root instead > of using "/sbin/service slimserver start" which starts it as the slimserver > user. Of course I'm starting the service as root. Obviously it creates those folders before it's switching to the slimserver user (under which it will _run_).
(In reply to comment #6) We're probably getting OT for this bug, but... > Hmm... where are your changes then? Since I changed the name to squeezecenter, I uploaded everything as trunk/platforms/redhat/squeezecenter.*. For now, you have to build the RPM yourself from those files. I want to do some more testing and tweaks (and get feedback) before I suggest someone from SD modify the build process to use it. Details at http://forums.slimdevices.com/showthread.php?t=39595 > Of course I'm starting the service as root. Obviously it creates those folders > before it's switching to the slimserver user (under which it will _run_). In my experience, if you start slimserver using "service slimserver start", it will properly create all of those files in the right places and appropriately owned by slimserver. If you just run slimserver.pl as root, it will create those files as root, or change them to root if they already exist. Also note that the RPM starts the service during %post so after installing the RPM you should just be able to go to the web UI. As you know, there may be a delay while it sets up the database the first time it's run. I installed the nightly RPM (not my version) just yesterday on CentOS 5 and everything worked as expected.
According to Dean, Konqueror is not supported. Should this bug be closed? I logged another bug about FireFox. It is #5923. That is probably a more important bug.
Closing, thanks
Reduce number of active targets for SC