Army_MoodBlue_mod skin crashes OpenVIX when trying to change skin, update EPG etc

[pjmangaloon]

Hi,
I was experimenting with different skins loaded from the Plugins menu and when I picked Army_MoodBlue_mod, it crashed when trying to swith to a different skin and even crashed when trying to update the EPG.

We are really sorry. Your receiver encountered a software problem, and needs to be restarted.
Please send the logfile /home/root/logs/Enigma2_crash_2022-03-22_13-35-40.log the Openvix forum
Your STB restarts in 10 seconds!
int', argument r of type 'int'
Additional information:
wrong number or type of arguments for overloaded function 'new_epoint'.
ePoint:
ePoint: :ePoint(int,int)
234.4105>
234.4105> pc: b55c6920
234.4106> Fault Address: 00000043
234.4106> Error code:: 23
234.4108> Backtrace:
234.4110> 13:35:40.5807 tOx77DD8J
234.4111> [OxB4F4DCOOJ
234.4111>
-—-—-FATAL SIGNAL (11)
234.4091> dig.applySkin()
234.4092> 13:35:40.5789 File "/usr/lib/enigma2/python/Screens/Screen.py", line 249, in applySkin
234.4095> 13:35:40.5792 File "/usr/lib/enigma2/python/Screens/Screen.py", line 277, in createGUIScreen
234.4098> File "skin applet", line 26, in
234.4101> 13:35:40.5797 File "/usr/lib/enigma2/python/enigma.py", line 1211, in_init_
234.4104> TypeError: in method 'new_epo

I've manually changed the skin in /etc/enigma/settings to a different skin, i.e. config.skin.primary_skin=Magic-FHD/skin.xml. I hope that works, will be restarting later.

Log file attached.

Thanks
---
Peter

[twol]

Hi,
I was experimenting with different skins loaded from the Plugins menu and when I picked Army_MoodBlue_mod, it crashed when trying to swith to a different skin and even crashed when trying to update the EPG.

We are really sorry. Your receiver encountered a software problem, and needs to be restarted.
Please send the logfile /home/root/logs/Enigma2_crash_2022-03-22_13-35-40.log the Openvix forum
Your STB restarts in 10 seconds!
int', argument r of type 'int'
Additional information:
wrong number or type of arguments for overloaded function 'new_epoint'.
ePoint:
ePoint: :ePoint(int,int)
234.4105>
234.4105> pc: b55c6920
234.4106> Fault Address: 00000043
234.4106> Error code:: 23
234.4108> Backtrace:
234.4110> 13:35:40.5807 tOx77DD8J
234.4111> [OxB4F4DCOOJ
234.4111>
-—-—-FATAL SIGNAL (11)
234.4091> dig.applySkin()
234.4092> 13:35:40.5789 File "/usr/lib/enigma2/python/Screens/Screen.py", line 249, in applySkin
234.4095> 13:35:40.5792 File "/usr/lib/enigma2/python/Screens/Screen.py", line 277, in createGUIScreen
234.4098> File "skin applet", line 26, in
234.4101> 13:35:40.5797 File "/usr/lib/enigma2/python/enigma.py", line 1211, in_init_
234.4104> TypeError: in method 'new_epo

I've manually changed the skin in /etc/enigma/settings to a different skin, i.e. config.skin.primary_skin=Magic-FHD/skin.xml. I hope that works, will be restarting later.

Log file attached.

Thanks
---
Peter

Not one of the OpenViX skins, and not updated for about 9 years, so not python3 compliant

[birdman]

Not one of the OpenViX skins, and not updated for about 9 years, so not python3 compliantWhy would a skin have Python code in it?

[pjmangaloon]

> Not one of the OpenViX skins, and not updated for about 9 years, so not python3 compliant

It in the list of Skins available in the plugins menu in OpenViX. I kinda works ish, I can go thru channels, EPG etc but it crashes when I try to change anything. If it doesn't work, can it be removed from the list of Skins?

Also, how can I manually change the skin? I tried changing config.skin.primary_skin=Magic-FHD/skin.xml in /etc/enigma/settings and it still reverted to Army_MoodBlue_mod on a GUI restart.

Thanks
---
Peter

[pjmangaloon]

> Also, how can I manually change the skin? I tried changing config.skin.primary_skin=Magic-FHD/skin.xml in /etc/enigma/settings and it still reverted to Army_MoodBlue_mod on a GUI restart.
Actually, restarting the GUI reverted to the broken skin, hard power cycling with the change in the settings file worked.

[dsayers]

Why would a skin have Python code in it?

One example is here https://github.com/openatv/enigma2/issues/2234 this change was causing issues with message box

[ccs]

> Also, how can I manually change the skin? I tried changing config.skin.primary_skin=Magic-FHD/skin.xml in /etc/enigma/settings and it still reverted to Army_MoodBlue_mod on a GUI restart.
Actually, restarting the GUI reverted to the broken skin, hard power cycling with the change in the settings file worked.

You need to stop enigma first (telnet init 4) before changing the settings file and init 3 to restart, otherwise your changes will be overwritten by the settings stored in memory.

Delete the troublesome skin folder to get rid of it, ViX will then revert to the emergency skin after a gui restart.

[twol]

Why would a skin have Python code in it?

Good question ….. but for example. https://github.com/OpenViX/skins/commit/737ecd5f925476f01f3d9a949ca50d0847c98332, which is probably the issue here

[Huevos]

Why would a skin have Python code in it?
All skins contain python code, e.g. TemplatedMultiContent and onLayoutFinish applets.

[birdman]

Good question ….. but for example. https://github.com/OpenViX/skins/commit/737ecd5f925476f01f3d9a949ca50d0847c98332, which is probably the issue hereCoudl be correct.

The skin does actually define two applets, both mention ePoint(...)and neither forces arg2 to be an int.

[pjmangaloon]

I wrapped non numeric parameters in calls to ePoint with int() in /usr/share/enigma2/Army_MoodBlue_mod/skin.xml, and it doesn't crash anymore when changing skins.