Aglare FHD by MNASR

There are 1,063 replies in this Thread which was already clicked 261,908 times. The last Post () by haldborg.

    When ente ajpanel -Channel tools, then exit the receiver restarts..This happens only with this skin

    Openatv7.5


    Quote from frank087234

    When ente ajpanel -Channel tools, then exit the receiver restarts..This happens only with this skin

    Openatv7.5


    Nothing related to the skin

    I tried and no problem

    Channel selection screen , menu , Ajpanel channels tool then exit . No restart


    Novaler pro - openatv 7.5.1 13/1/2025

    My box is sf8008, tried fresh openatv 7.5.1 and still same problem.

    Quote from odem2014

    I tried and no problem

    Channel selection screen, menu, Ajpanel channels tool then exit. No restart.

    If you do exactly the above, there is no problem.


    There is such a problem when you perform an action from within the "Channel tools" e.g. clear Zap History, find a channel, etc.

    The box sometimes restarts when exiting the AJPanel menu or "Channel Selection" context menu.


    frank087234


    The problem is definitely not caused by AJpanel or the Aglare skin. It must be due to OpenATV.


    I tested OpenPLi-GCC-14.2-sf8008 image with Aglare skin and everything works without a problem.

    When using OpenATV-7.5.1, often enigma restarts when I exit Channel tools.

    • Official Post

    From I.A. notes (chatGPT)


    Quote

    The error log you provided indicates a segmentation fault that occurred in Enigma2, with some key issues in the skin processing and a fatal signal leading to a crash.

    Here are the main points of interest from the log:

    1. TypeError in isinstance(): The error isinstance() arg 2 must be a type, a tuple of types, or a union suggests that somewhere in your skin processing, an invalid type is being passed to isinstance(). The second argument of isinstance() must be a type, a tuple of types, or a union, and the error shows that something else was passed.
    2. Segmentation Fault (Signal 23): The segmentation fault happens after this error. A segmentation fault typically occurs due to invalid memory access, such as accessing a memory location that the program is not allowed to read or write. In this case, it's happening within the Enigma2 process.

    Troubleshooting Steps:

    1. Check Skin File:
    2. Skin Widget Types:
    3. Check for Memory Access Issues:
    4. Revert to Default Skin:
    5. Debugging Enigma2:
    • Review the skin file for any issues, particularly around widget definitions or custom classes that could be causing the invalid type to be passed to isinstance().
    • The error indicates this is happening within the processWidget, processPanel, or processScreen functions, so it's likely tied to the skin processing code in that area.
    • Ensure that all widgets in your skin files are correctly defined. If you're using custom widgets or extensions, verify that they are being passed to isinstance() correctly (i.e., making sure the second argument is a valid type or tuple).
    • The segmentation fault (Fault Address: 00000094) could be due to invalid memory access when Enigma2 tries to read the skin or load some components. It's worth checking if there are any incorrect memory references in your code or skin files.
    • If this issue started after modifying the skin, try reverting to the default skin to see if the problem persists. If the default skin works, it confirms the issue is within your custom skin.
    • You can increase the Enigma2 debug level and check logs more thoroughly to see if there's a more specific cause of the segmentation fault that can give you clues about where to focus.


    Senza titolo.png

    Quote from Lululla

    From I.A. notes (chatGPT)


    Quote

    The error log you provided indicates a segmentation fault that occurred in Enigma2, with some key issues in the skin processing and a fatal signal leading to a crash.

    Here are the main points of interest from the log:

    1. TypeError in isinstance(): The error isinstance() arg 2 must be a type, a tuple of types, or a union suggests that somewhere in your skin processing, an invalid type is being passed to isinstance(). The second argument of isinstance() must be a type, a tuple of types, or a union, and the error shows that something else was passed.
    2. Segmentation Fault (Signal 23): The segmentation fault happens after this error. A segmentation fault typically occurs due to invalid memory access, such as accessing a memory location that the program is not allowed to read or write. In this case, it's happening within the Enigma2 process.

    Troubleshooting Steps:

    1. Check Skin File:
    2. Skin Widget Types:
    3. Check for Memory Access Issues:
    4. Revert to Default Skin:
    5. Debugging Enigma2:
    • Review the skin file for any issues, particularly around widget definitions or custom classes that could be causing the invalid type to be passed to isinstance().
    • The error indicates this is happening within the processWidget, processPanel, or processScreen functions, so it's likely tied to the skin processing code in that area.
    • Ensure that all widgets in your skin files are correctly defined. If you're using custom widgets or extensions, verify that they are being passed to isinstance() correctly (i.e., making sure the second argument is a valid type or tuple).
    • The segmentation fault (Fault Address: 00000094) could be due to invalid memory access when Enigma2 tries to read the skin or load some components. It's worth checking if there are any incorrect memory references in your code or skin files.
    • If this issue started after modifying the skin, try reverting to the default skin to see if the problem persists. If the default skin works, it confirms the issue is within your custom skin.
    • You can increase the Enigma2 debug level and check logs more thoroughly to see if there's a more specific cause of the segmentation fault that can give you clues about where to focus.

    Is the skin mentioned here refer to algare or skin of AjPanel itself, as far as I know, there are no screens related to AjPanel in algare skin.


    Plus all actions prior crash done on AjPanel not the skin itself,


    Just my point of view

    • Official Post

    this crash happens often on atv, maybe also on other images, tonight my wife changed channel and it happened again..

    -------FATAL SIGNAL

    It is not abnormal.

    But without a debug or other tests you can not say if it is the skin or something else.

    Quote from Mahmoud Hussein

    I think the simple way to try another skin and perform the same sequence if the same crash happens, means the problem is not related to algare

    it is between the image and AJPANEL

    I already did it on my box and no problem .

    Maybe image error in some updates

    So I mentioned what I tested , box name , image name and version , and date of update .

    The problem mention happened with me with keyadder plugin after switching the option to use custom path . I can't remember in last time it occurred, what image I was using ,

Enigma2 skins for oe-alliance based images.

Enigma2 skins for OpenATV, OpenDroid, OpenEight, OpenHDF, OpenNRF, OpenSPA, OpenViX and Pur-E2 images.

Participate now!

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

Register Yourself Login