It's in the repo just use the GUI upgrade button to get it.
It's in the repo just use the GUI upgrade button to get it.
Thanks for getting this out so quickly, Andrew. *I updated to LMS 7.7.1 from LMS 7.7.1 RC1 and the new version works well, as expected.
Some users who just upgraded to LMS 7.7.1 have run into problems: the VB GUI doesn't work, and upgrade (via "yum clean all; yum update" from the command line) is also broken.
See*Help!!….SBS 7.7.1 upgrade broke something*and*vortexbox-2-0-update-your-system-regularly*for user error reports.
Andrew tells me this is due to a bug in an early version of the LMS 7.7.0 rpm package that deleted a symbolic link to libbz2.so.1. Andrew has provided a fix for those encountering this bug. Login to your VB and enter
*ln -s /lib/libbz2.so.1.0.6 /lib/libbz2.so.1
======================
Andrew tells me this is due to a bug in an early version of the LMS 7.7.0 rpm package that deleted a symbolic link to libbz2.so.1. Andrew has provided a fix for those encountering this bug. Login to your VB and enter
*ln -s /lib/libbz2.so.1.0.6 /lib/libbz2.so.1
================
yep, I used WebGUI to update my 1.10 system to 7.7.1 today (from a prior 7.7.1rc1) and had the no access to webgui problem afterwards. logging into VBA and using above command restored access.
Hi all, I have some major confusion.* My 3TB Vortexbox Appliance has the latest software updates, including for Squeezebox server.* When I connect via the 64 bit Win7 laptop I normally use to access/run the VBA, everything looks normal.* When any other computer on my home network connects to the VBA, I see an old version of SBS.* How is this possible?* I'm just using a browser to point to the VBA, and SBS is only resident on the VBA (and my SB Touch, maybe, but that is up to date, too). There is no SBS loaded on the other pc's running XP, so how can the version of SBS change depending on which pc accesses the network device via a browser?* Sorry if this is an exceptionally dumb question or already answered, I have searched the forum a lot and keep finding far too many hits to read them all. Jim
maybe you need to clean your browser cache
Thanks, Firedog, that seems like a sensible suggestion, but...
-Why would two computers that had never connected to the VBA before, as in literally never, have any cached information corresponding to outdated SBS software? One of them had never even been on the network before (see more below).
-Furthermore, when I did try to connect the two new computers to the VBA for the first time, it was well after installing all the new upgrades and updating plugins to the point where no upgrades were indicated on the in any VBA control screen/GUI on the laptop that normally runs the VBA (no messages like "plugins have been updated, please restart").*
-One of this computers is my older son's laptop, and he didn't even live at home when I installed the VBA.* I tried to connect him when he came home from College for the winter holiday.* He can play the files locally with no problem using MediaMonkey (free), as can the other computer.
*
Not that I'm going to be stubborn, I'll clean the caches and report back.* I had thought I had raised my sons to know better and would have expected their caches to be*clean (I clean mine all the time, like 3 or 4 times a day or more), but maybe they've been secretly slovenly in their pc habits.
*
Best wishes, Jim
This is obviously not a VortexBox problem, but a problem with your Windows machines or the browsers you're using, or the URL you're entering.
Have you tried using the IP address of the VB when accessing the LMS web interface? E.g. http://192.168.1.152:9000 on my network. Try this instead of http://vortexbox:9000. Of course, use the correct IP address for your VB.
Then go to the LMS > Settings > Information page and report the version of LMS that is reported there.
Also, login to your VB; see http://info.vortexbox.org/tiki.....page=Login
Then enter
rpm -q logitechmediaserver
and report the results.
Sorry, have been swamped by work.* Will report back.* I agree, doesn't seem possible it is VB related and is likely Windows or browser related. Best wishes, Jim
Bookmarks