Testers required for OpenViX Python 3 images

[ccs]

This might be a clue as well.....

< 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.

 

[thecaretaker]

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.

 

[birdman]

All I've done is check samba (for the umpteenth time), using the gui, from a fresh flash, and report the findings, I'm 100% sure what I've posted is correct.

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.

I've never heard of samba-common, I doubt anybody else has either, and from where I'm sitting it's not relevant.

Well, it is the package that would contain a new smb,conf file, so it is relevant.

 

[birdman]

I reckon they're the first two highlighted in red in post #835.

I'd agree with that.

 

[ccs]

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.

Ok, but as it is already installed in a new image, I don't need to worry about it directly, config files may change but they then get overwritten by a settings restore.

 

[Huevos]

I have a problem, when I go to setup/user Interface/Skin Setup/Skin I get the spinner and box will reboot in 10 seconds. It did the same in the previous 5.5.015 image. Now have 5.5.016.

Here is the log report
View attachment 62692

I'm guessing this is the problem.

< 413.4050> File "/usr/lib/enigma2/python/Screens/Screen.py", line 249, in applySkin
< 413.4055> self.createGUIScreen(self.instance, self.desktop)
< 413.4055> File "/usr/lib/enigma2/python/Screens/Screen.py", line 279, in createGUIScreen
< 413.4060> f()
< 413.4060> File "/usr/lib/enigma2/python/Screens/SkinSelector.py", line 73, in layoutFinished
< 413.4063> self.refreshList()
< 413.4063> File "/usr/lib/enigma2/python/Screens/SkinSelector.py", line 142, in refreshList
< 413.4066> self.loadPreview()
< 413.4067> File "/usr/lib/enigma2/python/Screens/SkinSelector.py", line 147, in loadPreview
< 413.4071> preview = self.currentEntry[7]
< 413.4072> TypeError: 'bool' object is not subscriptable
< 413.4072> [ePyObject] (CallObject(<bound method NumberActionMap.action of <Components.ActionMap.HelpableNumberActionMap object at 0xab697e20>>,('OkCancelActions', 'ok')) failed)
< 417.0204> [gRC] main thread is non-idle! display spinner!

Please give an exact list of the skins you have loaded.

 

[Huevos]

I've tried changing my backupmanager directories to include just what I think is needed for samba...

config.backupmanager.backupdirs=[............., '/etc/auto.network', '[COLOR="#FF0000"]/etc/samba/smb-user.conf[/COLOR]', '[COLOR="#FF0000"]/etc/samba/private[/COLOR]', '/usr/keys', '/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/providers/terrestrial_finder.xml', '/usr/script', '[COLOR="#FF0000"][B]/etc/samba[/B][/COLOR]']

but those of you still with us will notice that backupmanager forces /etc/samba onto the end of the settings file as well. I give up.

See if this fixes for you... hopefully this does not cause other problems.
https://github.com/OpenViX/vix-core/commit/a52b6c292c9b3f7d2167666d28ca8724dae34361

 

[Huevos]

New Py3 build (5.5.017.002), ... and now with picon feeds.

 

[ccs]

See if this fixes for you... hopefully this does not cause other problems.
https://github.com/OpenViX/vix-core/commit/a52b6c292c9b3f7d2167666d28ca8724dae34361

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.

config.backupmanager.backupdirs=.......'/etc/auto.network', '[COLOR="#0000CD"]/etc/samba/smb-user.conf[/COLOR]', '[COLOR="#0000CD"]/etc/samba/private[/COLOR]', '/usr/keys']

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.

Begs the question what if someone really wants to backup /etc/samba?

 

[ccs]

I've backed up, flashed and restored 5.5.017.002 with /etc/samba edited out and all looks good ....

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           [COLOR="#FF0000"]772 Dec 31  2020 smb-user.conf[/COLOR]
-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

[COLOR="#FF0000"]/etc/samba/private:[/COLOR]
-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:~#

 

[Huevos]

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.

config.backupmanager.backupdirs=.......'/etc/auto.network', '[COLOR="#0000CD"]/etc/samba/smb-user.conf[/COLOR]', '[COLOR="#0000CD"]/etc/samba/private[/COLOR]', '/usr/keys']

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.

Begs the question what if someone really wants to backup /etc/samba?

Doesn't make sense system files being overwritten. Anyway if they want they can add the folder. Let's see it anyone complains.

 

[ccs]

Doesn't make sense system files being overwritten. Anyway if they want they can add the folder. Let's see it anyone complains.

Not sure I understand, if /etc/samba is in your settings file it make the changes to backupmanager redundant unless you remove it (from /etc/enigma2/settings).

 

[Huevos]

Not sure I understand, if /etc/samba is in your settings file it make the changes to backupmanager redundant unless you remove it (from /etc/enigma2/settings).

If I make changes to BackupManager that is going to only affect new backups, not current ones.

Start with the correct files in /etc/samba. Make a new backup. Now flash and restore with the new backup.

 

[ccs]

If I make changes to BackupManager that is going to only affect new backups, not current ones.

Start with the correct files in /etc/samba. Make a new backup. Now flash and restore with the new backup.

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.

 

[Huevos]

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...a3e9f6e9651e997002f4943801e44ed450R1179-R1180

 

[birdman]

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.

The original log also included:

< 413.3938> [Skin] Warning: Skin screen 'SkinSelector' rejected as it does not offer all the mandatory widgets 'skins, preview'!
< 413.3939> [Skin] No skin to read or screen to display.

which might be an issue?

(Unrelated: and that log also included a long traceback dump from, probably, some transcoding code.
Looks like someone left some debug code in place in production code?).

 

[ccs]

Yeah you're getting old. I commented out the full folder scan.

https://github.com/OpenViX/vix-core...a3e9f6e9651e997002f4943801e44ed450R1179-R1180

Well, the penny may now be dropping, are you saying that even though /etc/samba is in the settings file, it doesn't actually get backed up?

I thought that bit of code was adding new entries to config.backupmanager.backupdirs=.

I'll have another play later.

 

[ccs]

Well, the penny may now be dropping, are you saying that even though /etc/samba is in the settings file, it doesn't actually get backed up?

I thought that bit of code was adding new entries to config.backupmanager.backupdirs=.

I'll have another play later.

If I put /etc/samba in the settings file, it gets backed up.

Is it the restore process that ignores it?

 

[BrokenUnusableAccount]

There's something wrong with EPG search.
It's been somewhat broken since at least 5.5.016.001.

For example if I press EPG and then with the current program hjgihlighted I press Yellow to search for programs in the EPG with the same name as the current program it will only find a few programs with the same name.
If I advance a day or two in the EPG and find another program in the future with the same name and press Yellow with the future program highlighted it will correctly search for all programs in the entire EPG with the same name.

Also I still think it's daft that the program names sometimes have invisible control characters in them so that searching on them sometimes produces weird unexpected results.
I think they should be removed as the EPG data is read from the program stream or whereever.

 

[BrokenUnusableAccount]

Ok, but as it is already installed in a new image, I don't need to worry about it directly, config files may change but they then get overwritten by a settings restore.

Samba-common might get updated by Menu / Information / About / Software Update.