I’ve just received my new Vero 5. It arrived in about a week, which is impressive as I reside on the other side of the planet.
The new box is replacing my 4+. I uploaded the backup of the old box and everything installed perfectly. Netflix needed a few tweeks but it’s up and running.
The issue is changing the location of the Vero 5’s backup from the inherited one from the 4+. The file location starts with nfs: a throwback from my original setup. I now have nfs shares set up via the fstab file, mounted on /mnt
If I use the ‘browse’ option to try to change the file location, it won’t let me access the root file system. I just get to the top of the nfs directory tree. How do I get to the menu that allows me to select the root file system?
The work around is to manually type the location in. It works, but if I go back to the ‘browse’ option, it still show the old nfs: location. Is this a bug, or am I missing something?
I’d suppose the manual fix would be to manually edit or just delete the settings file in question and restart Kodi. The file would be found at… /home/osmc/.kodi/userdata/addon_data/script.module.osmcsetting.updates/settings.xml
I believe that the “browsed” backup location and the “typed” backup location are both stored as individual settings, and the “typed” backup location takes precedence. However, when you browse again, it will use the “browsed” backup location as the starting point. If that makes sense?
So not a “bug”, but perhaps a “quirk”.
There relevant settings in the settings.xml are
location_selection : set to 1 if the user has chosen to type a backup location and it then takes precedence
backup_location : the "browsed" backup location
backup_location_typed : the "typed" backup location
As to why you can’t break out of the nfs: directory tree when browsing, I do not know
The typed location works, the backups are going to where they’re supposed to, but when I go back to the “browsed” location it still contains the old ‘nfs’ location and I can’t get out of it.
I haven’t tried editing the .xml file as it’s not a show stopper.
It’s not really an issue for me as the nfs location on /mnt is straight forward. It would be more of an issue on set up if there were lots of levels to negotiate and with the risk of typos.
It’s something the developers can look at in slow time.
As workaround, first try to stop the mediacenter, make your changes and then restart the mediacenter. Some settings of MyOSMC will be only saved if you exit/stop the mediacenter.
sudo systemctl stop mediacenter
edit the file /home/osmc/.kodi/userdata/addon_data/script.module.osmcsetting.updates/settings.xml
