This might be a clue as well.....
Code:< 325.7679> [Skin] Error: Default skin '/usr/share/enigma2/ViX-Night-HD/skin.xml' is not readable or is not a file! Using emergency skin.
This might be a clue as well.....
Code:< 325.7679> [Skin] Error: Default skin '/usr/share/enigma2/ViX-Night-HD/skin.xml' is not readable or is not a file! Using emergency skin.
I use Skin VixBMC 1080 but Vix-Night-HD is included in the image, just not used.
EDIT SORTED:
OK, I flashed the image again without plug-in back up (just settings). Standard skin worked fine. Was able to switch skins.
Installed Vix VixBMC 1080 from the plugin downloads. switched to it from the Skins option, worked fine.
I went back to change the skin and got the crash again. So it must be an issue with the VixBMC 1080 skin for some odd reason. It works once chosen.
Last edited by thecaretaker; 14-10-21 at 21:06.
VU+ Duo 4K SE
The end result is. A flash and restore will result in you putting an old smb.conf in place if there is a newer one.
What I was saying was that installing samba can touch /etc/samba, as it pulls in samba-common. Except that this is part of teh base image, so opkg knows it is already installed so doesn't bother to do it again.
Well, it is the package that would contain a new smb,conf file, so it is relevant.I've never heard of samba-common, I doubt anybody else has either, and from where I'm sitting it's not relevant.
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
ccs (15-10-21)
See if this fixes for you... hopefully this does not cause other problems.
https://github.com/OpenViX/vix-core/...ca8724dae34361
ccs (15-10-21)
New Py3 build (5.5.017.002), ... and now with picon feeds.
It looks like config.backupmanager.backupdirs= entries are created the first time backupmanager runs, so running after a flash without a settings restore puts in the two samba references needed.
However, a settings restore will always have /etc/samba to contend with, so I guess backupmanager needs to remove the entry if it exists, or it needs editing out by hand.Code:config.backupmanager.backupdirs=.......'/etc/auto.network', '/etc/samba/smb-user.conf', '/etc/samba/private', '/usr/keys']
Begs the question what if someone really wants to backup /etc/samba?
Last edited by ccs; 15-10-21 at 16:25.
I've backed up, flashed and restored 5.5.017.002 with /etc/samba edited out and all looks good ....
Code:root@vuultimo4k:~# ls -lR /etc/samba /etc/samba: drwxr-xr-x 2 root root 4096 Oct 15 16:35 distro -rw-r--r-- 1 root root 20 Oct 5 21:31 lmhosts drwxr-xr-x 2 root root 4096 Oct 15 16:38 private -rw-r--r-- 1 root root 772 Dec 31 2020 smb-user.conf -rw-r--r-- 1 root root 95 Oct 5 21:31 smb.conf /etc/samba/distro: -rw-r--r-- 1 root root 61 Oct 5 21:31 smb-branding.conf -rw-r--r-- 1 root root 1516 Oct 5 21:31 smb-global.conf -rw-r--r-- 1 root root 586 Oct 5 21:31 smb-shares.conf lrwxrwxrwx 1 root root 13 Oct 15 16:35 smb-vmc.conf -> smb-vmc.samba -rw-r--r-- 1 root root 29 Oct 5 21:31 smb-vmc.samba /etc/samba/private: -rw------- 1 root root 430080 Dec 31 2020 secrets.tdb -rw------- 1 root root 204 Jan 18 2021 smbpasswd -rw-r--r-- 1 root root 80 Dec 31 2020 users.map root@vuultimo4k:~#
Every settings file for every ViX user will include /etc/samba in config.backupmanager.backupdirs=,
so a new backup will grab all files in /etc/samba, which defeats the object of the exercise?
/etc/samba may be up-to-date today, but it will lose any future updates.
Or maybe I really am getting old.
Yeah you're getting old. I commented out the full folder scan.
https://github.com/OpenViX/vix-core/...450R1179-R1180