Chocholousek Picons updater (Enigma2 plugin)

Hi Erling strand .

You can to try checking the disk functionality... also the correctness of the destination directory... and the capacity of the available space, via a terminal connection to the set-top box (ideally using the PuTTY application, via SSH or Telnet protocols).

mount

ls -al /media/usb/zzpicon

df -h

I don't know what you're doing wrong. Maybe you used a dot instead of a slash (you have to use a slash at the beginning of the path). Maybe there's a wrongly named, created directory on the disk (i.e. the directory doesn't exist - with the wrong name). You need to check more things and verify them. You can also verify with an FTP connection to the set-top box, where you check for the existence of the directory in the target path.

So you had the wrong directories. After changing them everything works ?

BTW, the directories that are built-in (as default dirs) in the Chocholousek Picons plugin are standard for most Enigma2 distributions. The most used directories for picons are these two:

/picon

/usr/share/enigma2/picon

Enigma2 needs a path to the picons, which is determined by its own algorithm. Not you. The plugin has the ability to edit and create its own directory, but that is for cases where the default path in the plugin is missing. It is not used to make Enigma2 change the path to the picons according to the user.

According to your screenshot, it is a non-existent folder where the plugin is trying to extract the picons.

Please... as I already wrote... use some default folder - the first one or the second one.

Theoretically... the path "/media/usb/picon" could or should also work. But not in all Enigma2 distributions. Of course, you can try it. So, create the folder "/media/usb/picon" with FTP connection. Then set this folder in the Chocholousek Picons plugin configuration. You must remove the other folders with picons (if you use other folders with picons).

Alternatively, you can enable debug logging in your Enigma2. Then raise an error. Find the debug log file using an FTP connection... and copy the last created debug log file... and paste it here in the discussion. There might be a more clearly readable error there. But first we need to make sure that you're not really doing anything wrong.

If there is a BUG in the Enigma2 algorithm, it will be a device-independent error. It is probably caused by a corrupted Enigma2 distribution or its outdatedness (outdated Enigma2 build). Try the directories / paths as I wrote.

What is the actual version and distribution of Enigma2 that you are using ?

Everything works. If it doesn't for you... then you have to do the diagnostics yourself again.