Chocholousek Picons updater (Enigma2 plugin)

There are 520 replies in this Thread which was already clicked 142,867 times. The last Post () by pinokio0.

    thanks for your response

    I use no Body image from Boxpirate

    DreamboxTwo

    Gigablue Quad 4K Pro

    Oh... I see now, this is the name of Enigma2. However, I don't know this "GP4.2 Nobody Image" at all. So I probably won't advise you. I couldn't find anywhere how to start debugging on it, or what Enigma2 core it's based on... or where it actually comes from. I also found some German discussion forum and download these Enigma2 images. But I didn't find anything else. No support forum for reporting bugs. On most Enigma2's that are used on Dreambox devices, installing 7z works. Moreover, I am not familiar with those "Dreambox" firmwares. I only know old Enigma2 cores. But it's a mystery why it doesn't work. On other "Dreambox" firmwares, installing 7z works OK.


    The debug file could show where the error occurs :-/.


    For example, try to connect via terminal / linux shell to the set-top box. Then try to examine the journal:

    journalctl -f -u enigma2 >> /tmp/journal.log - the entire system log will be displayed, with a filter for "enigma2" processes, and this will be redirected or it will be added to our file "/tmp/journal.log"

    journalctl --since "1 hour ago" - display syst. log from the current time, 1 hour backwards (probably doesn't work under Enigma, but only in full-fledged Linux)


    But I can't say whether a journal is used there. I am not at all familiar with this offshoot of the Enigma2 firmware and I don't even know what it came from.

    Work fine with Nobody image.


    screenshot (1).png

    screenshot (2).png

    screenshot (3).png

    screenshot (4).png

    maho33


    Try reboot of the set-top tox OR try quick restart of the Enigma2 / GUI.


    If it doesn't help, you're probably using an alternative (non-original) SKIN that can't find picons in the appropriate folder or uses a bad algorithm for finding picons on the disk in the set-top box. This is usually solved by creating a symbolic link to directory with picons for SKIN as well or by setting a directory path to picons in the SKIN configuration.

    This needs to be addressed with the team that developed the SKIN... or with the creators of Merlin 2.5 of the Enigma2 distribution. They have a bad algorithm there, for using or searching for picons.


    I think one directory is enough for SKIN. All modern SKINs these days should be able to automatically adjust the size of the icons. That is that they must appear correctly in the channel list and also in the InfoBar.


    Or the alternative solution is, as I wrote, to create a symbolic link (make a virtual directory), where SKIN will then find the necessary picons.


    If it is the case that SKIN already uses one directory for InfoBar picons + channel list, then it is enough to use only this single directory and direct the picons there (in the configuration of the ChocholousekPicons plugin, browse the path to this SKIN-directory).

    Quote from s3n0

    maho33


    Try reboot of the set-top tox OR try quick restart of the Enigma2 / GUI.


    If it doesn't help, you're probably using an alternative (non-original) SKIN that can't find picons in the appropriate folder or uses a bad algorithm for finding picons on the disk in the set-top box. This is usually solved by creating a symbolic link to directory with picons for SKIN as well or by setting a directory path to picons in the SKIN configuration.


    Quote from s3n0

    maho33


    Try reboot of the set-top tox OR try quick restart of the Enigma2 / GUI.


    If it doesn't help, you're probably using an alternative (non-original) SKIN that can't find picons in the appropriate folder or uses a bad algorithm for finding picons on the disk in the set-top box. This is usually solved by creating a symbolic link to directory with picons for SKIN as well or by setting a directory path to picons in the SKIN configuration.

    have tried restarting the box several times it's the same

    it's hdsuisse .fhd skin

    OK, then you have to write to the creators of this SKIN to fix the error.


    Or... turn on debug mode in your Enigma2 distribution (Merlin 2.5) if possible... and then send the generated debug log file... where it should be displayed error when trying to open a picon via the InfoBar algorithm.


    What exactly SKIN are you using ? Is there any Github or open code on the internet for this SKIN? I would look to see if I can find something there.


    However, it would be best if you provided a debug log file from your Enigma2 distribution, after triggering the bug (opening the InfoBar - without the icon displayed).

    Yes, i know use same skin.

    send this commend via telnet depends where you store picon:

    for Merlin image:

    ln -s /usr/share/enigma2/picon_220x132 /usr/share/enigma2/picon

    ln -s /usr/share/enigma2/picon_220x132 /usr/share/enigma2/picon_50x30

    oder wenn in data:

    ln -s /data/picon_220x132 /data/picon

    ln -s /data/picon_220x132 /data/picon_50x30

    telnet command is not working my friend

    Whichever path you choose maho33, I would also like to mention that up to 3 configuration profiles can be used in the Chocholousek Picons plugin. This means that it is necessary to use 50x30 picons and 220x132 at the same time, so you can set it up.


    For example, in configuration profile 1, picons with one resolution are downloaded to the first folder, and then, another picons will downloaded to another folder - through configuration profile 2.


    But I think it's better to create symbolic links, as PakTo mentioned. If SKIN can automatically transform the resolution of picons, it is better if you have only one common directory for picons.


    I personally would delete the other picons. And I would use one "/picon" folder right in the root. And then I would direct symbolic links into it:

    Code
    mkdir -p /picon
ln -s /picon /usr/share/enigma2/picon
ln -s /picon /usr/share/enigma2/picon_220x132
ln -s /picon /usr/share/enigma2/picon_50x30

Your source for Enigma2 picon plugins

Find downloads and support for tools that automatically fetch, update, and display channel logos in your receiver's interface. Discover essential Enigma2 picon plugins. Access downloads and support for the latest tools to manage and display channel logos automatically.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login