Posts by s3n0

Hi.

Thanks for the bug report. It's really weird.

It would help to turn on debugging in Enigma2 + reboot. And send me created debug log file... here... into the discussion... or via a private message - of course, only after the error appears, so that it is written into the debug file.

In the last OpenATV, which version do you mean exactly? I have OpenATV 7.3 and there is no problem.

It looks like somewhere (I don't know where) the module "Plugins.Extensions.ChocholousekPicons.plugin" is being imported as the plugin. Probably in Enigma2 code. And this algorithm subsequently fails... I don't know why.

Your last post is the same idea as:

- I can get water in a glass ! How do you take water into a glass ?

If you know that, then why are you asking ? If you knew that... if you at least read the "article" about installing Oscam manually... you would find out how to diagnose Oscam startup.

Simply start by using the man-page for Oscam:

/usr/bin/oscam --help

(you must know the correct name of the Oscam binary)

You can also try to restart or start the Softcam, using the "init.d" shell-script. Maybe this action will tell you something more about the problem:

/etc/init.d/softcam restart

If it doesn't work, the problem will be in the compatibility of the libraries (probably in ATV 7.4 there are new libraries and the old ones are removed and therefore it is necessary to add symbolic links - to old libraries, to start new libraries... but compatibility is never one hundred percent guaranteed). However, you will see an error about the libraries when you try to start Oscam manually (in the terminal connection to the set-top box).

Do I really have to remind you of all this? You write nonsense here about some non-functional Oscam, but you don't write anything about WHY Oscam doesn't want to start. First write why it doesn't want to start. Then ask for a solution to the problem. You don't even know where the problem is. So why are you asking about a solution to a problem that you yourself cannot identify and determine?

OpenATV 7.4 is currently still under development ! Do not use this OpenATV 7.4 if you are not an experienced user !

Why the hell are you using it ?! These test versions (beta / alpha - development versions) are intended exclusively for developers or experienced IT experts. Not for people who can't deal with stupid Oscam (I mean it honestly and no offense... please).

You can also install Oscam manually (if you have the appropriate Oscam binary file). Instructions on how to do this can be found, for example, at the begin of my startup init.d shell-script or also in a small and brief article.

Oh... OK... so, it's good that there is the same standard and service reference codes. But that depends on chocholousek , whether he will create picones for the USA as well. He already has a lot to do :-/. Maybe a donation would be useful or someone who can donate Chocholousk for his work, for example from the USA :-).

However, I can't really say... that what and how. Making picons is Chocholousk's hard work. You have to contact him and he will tell you himself... whether he has free time, willingness, resources for service reference codes, ... etc. ... for the creation and care of other picons :-/.

Hi cpr43 .

This is more of a question for the creator and designer of the picons - a question for chocholousek . I am just a plugin developer for these beautiful picons from Chocholousek, which are available in all the most popular image resolutions.

I really don't know if Chocholousek has the desire and free time to create picons even for satellites on the North American continent (USA). That would probably also mean reworking the plugin for changing the US / EU locations.

What are the service reference codes and standards in the USA for satellite reception ? Are they the same as in Europe ? Does this mean that DVB-S2 is used there for satellite TV reception ?

If you want to make a CFE boot-loader backup, I also own a Vu+ Solo SE V2, so I could make a CFE backup. But I don't know how to do it in Linux Shell... or if it's even possible in Linux Shell.

I wouldn't bother with that. I would buy a new device. For example, Vu+ Zero 4K.

Damage to the CFE-bootloader code block is unlikely, as the CFE bootloader itself works OK. CFE booloader already reports the error - when it is booting. So it's probably not a bug in the CFE bootloader itself.

I have a bootloader for Vu+ Solo SE (also V2 is the same) in my PC, but I don't know where I got it from. Of course, it is flashed by hardware - via RS232. The flashing procedure should also be sufficient via a USB memory stick (it is the same procedure as when flashing Enigma2).

So I thought... that maybe you used the wrong firmware... and changed the names of the folders to your liking... and then overwrote the firmware in your device with a bad version, intended for a different type of Vu+.

That's right, there are some errors at the end of the CFE log.

However, you asked about flashing procedures, and when the CFE bootloader responds and can load files from a USB memory stick, the error lies elsewhere.

The cause can be any HW problem. For example, problems with internal flash memory or RAM. It may not be a directly faulty part of the cells / blocks in the memory modules, but it can be, for example, the power supply of the memories. The cause can be, for example, "cold connections" on the PCB (poor connections). It's hard to say where the error is. It could be anything else.

You should buy a new set-top box when you have these hardware problems.

Or try asking on some Vu+ focused discussion forum.

Hi hecha71 .

The standard method of flashing the set-top box via an inserted USB memory stick - does not work ? I mean this method (valid for all Enigma2 firmwares): https://wiki.openpli.org/Recei…ow_to_flash_Vu.2B_Solo_SE

Note for OpenATV firmware:

In case of using OpenATV firmware, delete the file named "splash.bin" from USB memory stick. This file will rewrite the logo of the Vu+ device that you see immediately after turning on the set-top box to the ATV design (you will see the ATV advertisement after turning on the set-top box). So it is better to delete this one file.

According to the attached log file, CFE works and normally searches for and tries to flash firmware from USB memory devices:

CFE initialized.
USB: New device connected to bus 2 hub 1 port 1
USB: Resetting device on bus 2 hub 1 port 1
USB: [Transfer error: 5]
USB: Device disabled due to communication error!
USB: Bus 3 Hub 1 port 1 in overcurrent state...not re-enabling power
waiting for usb...done
checking usb
No Priority Usb
checking front key
readFrontKey 0 0
Checking usbdisk0:/vuplus/solose/ignore.update......NO
Checking usbdisk0:/vuplus/solose/force.update......NO
Checking usbdisk0:/vuplus/solose/cfe_cfe_auto.bin......NO
Checking usbdisk0:/vuplus/solose/root_cfe_auto.bin......NO
....NO
Checking usbdisk0:/vuplus/solose/splash_cfe_auto.bin......NO
Checking usbdisk0:/vuplus/solose/kernel_cfe_auto.bin......NO

Of course... as first... it is recommended... to uinstall the old one.

Quote from merouane1

Merci pour la mise à jour. Jais un problème des picons sur le Sat Nilesat ( 7°W) la chaine Algerien mais le picone ne correspondant pas à la chaine et il y a des chaines non pas des picone et merci.

Hi. Try it here: Picons by Chocholoušek

Quote from viliev

Would you like to tell me how to make "loop-test-output.txt"

Hi.

Use the first code (at the top) from my post #372 :

Post

RE: Chocholousek Picons updater (Enigma2 plugin)

Exactly Warder 👍

I didn't give it a chance at first. But you're already the second person to confirm it to me. Namely... that there really could be a problem in the userbouquet files.

I had all the "userbouquet.*.tv" files supplied by viliev checked in a loop (I have them in a private message as a ZIP archive) and indeed there are some files with the wrong format: ISO-8859-1, MacRoman, Windows-1252, ASCII, ... etc. .
(Code, 7 lines)


//////////// EDIT :

Hm, that's weird. When I open the files…

s3n0

Dec 17th 2023

However, as first, edit the path to the directory in the 2nd line of code, to "/etc/enigma2/userbouquet.*.tv".

You can first copy the entire code into a text editor on your PC. Then edit the mentioned directory. And finally, copy the text again in the text editor, to the Windows clipboard, using the CTRL+C keyboard shortcut.

1. Connect via Telnet / SSH protocol to your set-top box

2. Then start the Python interpreter - command: python<ENTER>

3. Next... you need to copy text... by marking text with the help of the mouse and using the keyboard shortcut CTRL+C... of the entire code

4. If you are using the PuTTY application as a terminal for Telnet / SSH connections, then, you just click on the PuTTY window with the mouse - with the right button ... and the content from the Windows system clipboard will be inserted (correctly: "sent") into the PuTTY terminal. (If nothing works, you can copy the lines one by one into the PuTTY terminal or you can rewrite the whole thing manually via the keyboard.)

Exactly Warder 👍

I didn't give it a chance at first. But you're already the second person to confirm it to me. Namely... that there really could be a problem in the userbouquet files.

I had all the "userbouquet.*.tv" files supplied by viliev checked in a loop (I have them in a private message as a ZIP archive) and indeed there are some files with the wrong format: ISO-8859-1, MacRoman, Windows-1252, ASCII, ... etc. .

import glob
bouquet_files = glob.glob("/tmp/u/userbouquet.*.tv")
for PATH in bouquet_files:
  print("%s ---- %s" % (chardet.detect(open(PATH, "rb").read()), PATH))
  with open(PATH, "r") as f:
    data = f.read()             # an error occured ?!

//////////// EDIT :

Hm, that's weird. When I open the files individually on the PC, they look fine in Notepad++. Maybe a BUG in Python 3 ? :-D

It is actually my fault that my plugin does not write the specific userbouquest file it is currently processing, in the debug log. I don't want to create an unnecessarily large "FLOOD" in the logs - while debugging Enigma2.

I discovered that the file "userbouquet.ciefpsettings_filmovi3.tv" could be faulty.

My conclusion:

I don't know if the problem is in the encoding of UTF-8 characters, but definitely these userbouquet files are not correctly encoded in UTF-8 ! As you can see on the attached screenshot, they contain meaningless characters, especially the 0xD0 character, which causes a BUG in Python, and which the UTF-8 decoder tries to decode in every possible way... but it doesn't always succeed. It is necessary to repair / edit these strange userbouquet files... or delete them altogether.

>>> bq_file = "/tmp/u/userbouquet.ciefpsettings_filmovi3.tv"
>>> with open(bq_file, "rb") as f:
>>>   data = f.read()
>>> type(data)
<class 'bytes'>
>>> data.decode('utf-8')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd0 in position 49451: invalid continuation byte
>>>

@zephy4

Yes I know. The plugin basically works everywhere and for everything. No one has reported this error. Only viliev reports a minor problem.

I'm trying to find out exactly what the problem is. So far we have only found out that it is a problem with detecting UTF-8 in userbouquet files - specifically in loading content from these userbouquet files.

The question now is whether this is a BUG:

- OpenATV 7.4-development

- Python (BUGs in Python itself are not unusual and sometimes happen)

- wrong format of userbouquets files

- an error in the source code of the plugin

I can use UTF-8 to load content from a file, but that's not a problem, since files are loaded by default as UTF-8. The problem is that the decoder sees the character 0x0D there, which is used when formatting Windows newlines 0x0D + 0x0A (CR + LF). Whereas for UNIX only character 0x0A (LF) is used.

The error can really be anywhere. Probably userbouquet files are edited by some plugin and put wrong character in formatting other than UTF-8.

OK, so please try this in both cases, in the Python interpreter, as I mentioned above:

import glob
bouquet_files = glob.glob('/etc/enigma2/userbouquet.*.tv')
bq_file = bouquet_files[0]
print(bq_file)
bq_contents = ''
with open(bq_file, 'r') as f:
  bq_contents += f.read()        # an error occured ?!
chardet.detect(open(bq_file, 'rb').read())['encoding']

Hi viliev

I couldn't find the OpenATV 7.4-devel version for the Vu+ Solo SE V2 anywhere on the internet, so unfortunately I can't test it myself.

If you want, you can create a BUG report for this "7.4-devel" version on the OpenATV discussion forum. You can also attach all the URLs what we discussed together + including of the CODE TAGs contents. You can also attach your userbouquet files to the OpenATV forum.

It seems to be really just a problem with the ATV 7.4-devel development version.

The error will probably be in the "UTF-8" decoding of your userbouquet files... however, the error may not be directly in the file but in the algorithm that reads the data from the file. I tried it now in OpenATV 7.3 @ Python 3.11.2 - in the official released version, and everything went OK. I simulated the activity of my plugin with your userbouquest files (copied into the "/tmp/u" folder):

root@vusolose:~# python
Python 3.11.2 (main, Feb  7 2023, 13:52:42) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import glob
>>> bouquet_files = glob.glob('/tmp/u/userbouquet.*.tv')
>>> bq_file = bouquet_files[0]
>>> bq_file
'/tmp/u/userbouquet.samsungtvplus_us.tv'
>>> bq_contents = ''
>>> with open(bq_file, 'r') as f:
...     bq_contents += f.read()
...
>>>
>>>#........all done ? ..... no error occurred

Btw, what version of Python does this ATV 7.4-devel use ? Please connect via Telnet / SSH to your set-top box and type the command "python --version".

If you could manage it... you can try the same... after connecting via Telnet / SSH to your set-top box. So, first you start the Python interpreter (write the command: python). Unpack / copy the userbouquets files into a temporary folder in the set-top box "/tmp/u" or change the name of the directory path to your own, i.e. from "/tmp/u" to "/etc/enigma2". And then proceed in the Python interpreter, according to the above steps.

You skipped the first step - check your files "userbouquet.*.tv" and "userbouquet.*.radio". There is probably an error in them, which Enigma2 cannot deal with, because it received an over-the-air update.

I have OpenATV 7.3 only and I have absolutely no problem with myself.

I can also... if I have free time... test the development version ATV 7.4... via OpenMultiboot... on my Vu+ device. And I'll see if the error manifests itself in me as well.

But first we will test your userbouquest files. If you can't manage it yourself (you haven't written anything about your IT skills yet), you can send them to me (preferably as one zipped file, of course).

Hi viliev

First of all, it should be noted that you are using OpenATV version 7.4, which is a test version intended for developers. Still, this version is not finished and is still under development. That is that errors may still appear randomly in Enigma2 during regular updates of this beta or alpha version. You mentioned two set-top boxes, so I assume that ATV 7.4 is installed on both of them.

Secondly, regarding the BUG, as you can see, the following problem occurs:

06:52:12.3825   File "/usr/lib/enigma2/python/Plugins/Extensions/ChocholousekPicons/plugin.py", line 1540, in proceedCfgProfile
06:52:12.3862     bq_contents += f.read()
06:52:12.3866                    ^^^^^^^^
06:52:12.3867   File "<frozen codecs>", line 322, in decode
06:52:12.3868 UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd0 in position 49451: invalid continuation byte

ChocholousekPicons source code: https://github.com/s3n0/e2plug…ugin.py#L1540C44-L1540C44

Enigma2 source code crashes for a partially known reason. However, since the ChocholousekPicons plugin runs at that moment only in a separate thread (i.e. a separate algorithm in the background), the entire Enigma2 (ATV 7.4) will not crash. Under normal circumstances, however, Enigma2 should crash (BSOD / GSOD will appear). Then subsequently, in the event of an error in the execution of the source code in the ChocholousekPicons plugin, it will terminate regularly + also with the error reported by the plugin: "No operation! Picon update failed!".

In the debugging information (debug-log file) it can be seen that the problem arises when reading the files "/etc/enigma2/userbouquets.*.tv" (userbouquets.*.radio) in connection with the decoding of UTF-8 characters. Specifically, there is a problem with decoding some character 0xD0.

You can try to check your userbouquest files to see if their encoding is correct and if, for example, some other plugin has written some wrong characters into them. If these userbouquets files are fine, try reporting a bug on the opena.tv discussion forum. Although... at this moment, ATV 7.4 is still under development. So you can... but you also don't have to... report this BUG. The choice is only yours. If this is really a bug of ATV 7.4, then probably the developers just didn't notice this bug and will fix it soon.

No, nothing arrived, sorry.

Try the following:

1. click on my nickname (under my avatar / my icon)

2. then click on "User" - i.e. a stick figure icon

3. where the context menu will appear... please choose the option: Create Conversation

4. put the name of the subject in the first field (for example "chocholousek picons plugin")... and then below, in the large field, you can write a private message... and of course it is also possible to attach attachments in this private conversation

I was wondering if you know how to turn on and get the debug file :). But you probably don't know that.

Here is "HowTo" for OpenATV:

MENU > Settings > System > Debug.... > Enable debug log = Yes

Then use the green button to save the settings and do a quick restart of Enigma. After running Enigma2, enter the ChocholousekPicons plugin again and trigger the error. All done. Now just enter the folder "/home/root/logs" via FTP connection and copy the latest debug log file to the PC. Send me this debug-log file in a private message.

Thanks.