Testers required for OpenViX Python 3 images

[Huevos]

So why do we need to reinstall from the feeds after restoring settings from other image?



Not impossible. The same problem would happen that could be got around in the same way.
But maybe different code does it in that case and does overwrite the oscam binary??

Not sure what you mean. If the plugin was downloaded first and then overwritten how would it be possible to move to the latest version?

 

[Huevos]

So we need to add b in url in custommix for encoded URLs?

No. They must already be byte strings otherwise this would happen:

Python 3.8.2 (tags/v3.8.2:7b3ab59, Feb 25 2020, 22:45:29) [MSC v.1916 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> url = "http%3a//iptv.url%3a8080"
>>>
>>> b"%" not in url[:10]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'in <string>' requires string as left operand, not bytes
>>>

 

[BrokenUnusableAccount]

Not sure what you mean. If the plugin was downloaded first and then overwritten how would it be possible to move to the latest version?

Perhaps I misunderstood you.
Latest version of what?

 

[Huevos]

Perhaps I misunderstood you.
Latest version of what?

Softcam.

For historic reasons softcams are stored in a backup by default.

Download "oscam-latest" from the feeds.

Make a backup.

Flash new image and restore the backup.

Softcam from the backup will be loaded into the image.

Next, during plugins restore, if the softcam was originally installed by opkg , the softcam will be download from the feeds and will be written over the top of the copy that came from the backup.

 

[BrokenUnusableAccount]

Softcam.

For historic reasons softcams are stored in a backup by default.

Download "oscam-latest" from the feeds.

Make a backup.

Flash new image and restore the backup.

Softcam from the backup will be loaded into the image.

Next, during plugins restore, if the softcam was originally installed by opkg , the softcam will be download from the feeds and will be written over the top of the copy that came from the backup.

You're describing upgrading to a new version of OpenViX, not a new version of oscam.
Though the former might include the latter.

 

[Huevos]

No, I am talking about a flash and restore, which may be done from the current version to the current version.

 

[stingray13]

Is there a tmnanosem2plus image available for test if not can I add it to the list, please?

 

[BrokenUnusableAccount]

No, I am talking about a flash and restore, which may be done from the current version to the current version.

Isn't that what I just said?

 

[Huevos]

Isn't that what I just said?

Flash and restore does not have to be to a newer version.

Anyway, the point of my post was to say the version from the feeds will win even if you have the softcam in your backup.

 

[dsayers]

I've noticed an odd bug on reboot the epg isn't restored. I have to manually download epg again after a GUI restart

Edit it was the crossepg test causing issues. I've uninstalled it and it seems fine. I didn't think crossepg would effect boot. Auto update crossepg was disabled.

 

[BrokenUnusableAccount]

In Softcam manager, Restart (yellow button) doesn't seem to really restart oscam for me. It just kind of pretends it's restarting it.

 

[ronand]

I've noticed an odd bug on reboot the epg isn't restored. I have to manually download epg again after a GUI restart

Edit it was the crossepg test causing issues. I've uninstalled it and it seems fine. I didn't think crossepg would effect boot. Auto update crossepg was disabled.

Crossepg is corrupting the data stored in epg.dat so it can't reload after a reboot.

 

[Huevos]

Crossepg is corrupting the data stored in epg.dat so it can't reload after a reboot.

Not corrupt. Written in the old format, so can't be read correctly.

 

[Huevos]

Is there a tmnanosem2plus image available for test if not can I add it to the list, please?

@stingray13, the tmnanosem2plus is available in the download folder.
http://images.satellites-xml.org/Py3/

 

[thecaretaker]

I did a software update and although SAMBA is running, I just can't connect to it from my TV. Tried removing it and adding again, checked password etc. Original image worked perfectly. I did notice some comment about SAMBA in the change log notes.

I looked at the SAMBA log and it is blank.

EDIT: I replaced the etc/Samba folder from the original release and replaced it in the newer image and it worked fine.

 

[ccs]

I did a software update and although SAMBA is running, I just can't connect to it from my TV. Tried removing it and adding again, checked password etc.
Original image worked perfectly. I did notice some comment about SAMBA in the change log notes.

I looked at the SAMBA log and it is blank.

EDIT: I replaced the etc/Samba folder from the original release and replaced it in the newer image and it worked fine.

Do you mean the original P3 image worked perfectly?

Also, when using the P3 image for the first time, did you perform a settings restore?

 

[ccs]

This is my working P2/P3 /etc/samba created some time ago (before P3) and kept in a settings backup (by default).

The changes in red are needed to make Network Browser work.

Where did you find the Samba change log, I'm pretty sure it's up-to-date.

root@vuultimo4k:~# ls -lR /etc/samba
/etc/samba:
drwxr-xr-x    2 root     root          4096 Jun 30 20:01 distro
-rw-r--r--    1 root     root            20 Dec 31  2020 lmhosts
drwxr-xr-x    2 root     root          4096 Jun 30 20:01 private
-rw-r--r--    1 root     root           772 Dec 31  2020 [COLOR="#FF0000"]smb-user.conf[/COLOR]
-rw-r--r--    1 root     root           744 Dec 31  2020 [COLOR="#FF0000"]smb-user.conf.orig[/COLOR]
-rw-r--r--    1 root     root            95 Dec 31  2020 smb.conf

/etc/samba/distro:
-rw-r--r--    1 root     root            61 Dec 31  2020 smb-branding.conf
-rw-r--r--    1 root     root          1457 Dec 31  2020 smb-global.conf
-rw-r--r--    1 root     root           586 Dec 31  2020 smb-shares.conf
lrwxrwxrwx    1 root     root            13 Jun 30 20:01 smb-vmc.conf -> smb-vmc.samba
-rw-r--r--    1 root     root            29 Dec 31  2020 smb-vmc.samba

/etc/samba/private:
-rw-------    1 root     root        430080 Dec 31  2020 secrets.tdb
-rw-------    1 root     root           204 Jan 18 15:30 smbpasswd
-rw-r--r--    1 root     root            80 Dec 31  2020 users.map
root@vuultimo4k:~# [COLOR="#FF0000"]cat /etc/samba/smb-user.conf[/COLOR]
## User changes to Samba config go here

## You can overrule the insecure defaults and enforce password
## protected access to shares by uncommenting the following
## line, including the secure settings:

[global]
#       include = /etc/samba/distro/smb-secure.conf
        [COLOR="#FF0000"]disable netbios = No[/COLOR]

## You can hide and veto access to certain directories, e.g. mount points of
## other boxes in order to prevent round trips through your LAN
## In Samba 4.x this needs to be configured per share:

[Root]
#       veto files = /ThisBox/OtherBox/AnotherBox/YetAnotherBox/
#       hide files = /ThisBox/OtherBox/AnotherBox/YetAnotherBox/

[Harddisk]
#       veto files = /ThisBox/OtherBox/AnotherBox/YetAnotherBox/
#       hide files = /ThisBox/OtherBox/AnotherBox/YetAnotherBox/
root@vuultimo4k:~#

 

[Huevos]

So how are we doing? Is everything perfect now?

 

[dsayers]

So how are we doing? Is everything perfect now?

Looking good here. No major issues here

 

[thecaretaker]

Do you mean the original P3 image worked perfectly?

Also, when using the P3 image for the first time, did you perform a settings restore?

Yes, I mean the original P3 image worked. I did a settings restore but not the plugin restore.

The update altered Samba somehow and wouldn't work. By replacing the etc/Samba folder from the original P3 into the updated P3, it worked.

Everything else seems to be working perfectly. I also had to install epg-refresh from the feeds when installing the original P3 as that was missing. But now working perfectly.