Forums

root@vuultimo4k:/hdd# vi enigma2_crash_1703111979.log
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 57, in action
    res = self.actions[action]()
  File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1006, in mainMenu
    self.session.openWithCallback(self.mainMenuClosed, MainMenu, menu)
  File "/usr/lib/enigma2/python/StartEnigma.py", line 295, in openWithCallback
    dlg = self.open(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/StartEnigma.py", line 308, in open
    self.execBegin()
  File "/usr/lib/enigma2/python/StartEnigma.py", line 233, in execBegin
    c.show()
  File "/usr/lib/enigma2/python/Screens/Screen.py", line 132, in show
    val.onShow()
  File "/openpli/oe/develop/build/tmp/work/all-oe-linux/enigma2-plugin-skins-e2darkos/1.0+gitAUTOINC+6d03eb0438-r0/image/usr/lib/enigma2/python/Components/Renderer/BoxLogo.py", line 66, in onShow
  File "/openpli/oe/develop/build/tmp/work/all-oe-linux/enigma2-plugin-skins-e2darkos/1.0+gitAUTOINC+6d03eb0438-r0/image/usr/lib/enigma2/python/Components/Renderer/BoxLogo.py", line 35, in setLogo
  File "/usr/lib/enigma2/python/Tools/LoadPixmap.py", line 24, in LoadPixmap
    raise Exception("Neither .png nor .jpg nor .svg, please fix file extension")
Exception: Neither .png nor .jpg nor .svg, please fix file extension
[ePyObject] (CallObject(<bound method ActionMap.action of <Components.ActionMap.HelpableActionMap object at 0xb14e3b68>>,('InfobarMenuActions', 'mainMenu')) failed)

Btw… nice that surprising x-mass wish…. But a pitty without going to default skin (via putty) the box becomes unusable with the e2os skin. Work-a-round is delete the skin row in /etc/enigma2/settings file to get back to our default skin.
Edited by littlesat, 21 December 2023 - 00:05.

Is this crash related to the VU+ vs Vu+ discussion? In which case it is easily fixed locally on the box, until we have a working develop build again.

This one is on multibox, not Vu+…. Crazy this stuff… but I’m afraid this is something different but I’m now not able to further investigate…
Edited by littlesat, 21 December 2023 - 00:48.

This is because of the new box branding stuff. The BoxLogo render has changed and now because on PLi the logos are missing still it crashes.

 

I have added an additional check for this in the renderer.

 

Maybe try the attached file it should not crash anymore at least not on that place.

Can you show me the diff or point me to the github…. At least for skins I think it should not crash here. I already thought this should be it. In addition the renderer and also the others should go to the image.
The boxinfo is in progress.
Edited by littlesat, 21 December 2023 - 07:54.

the change is here

 

https://github.com/D...8efe7a9c533ef59

 

And ok renderer can be in the core files...But not all distros that using the skin agreed to that yet

Sounds we need a different recipe here… at least I think you understand having renderers and converters dedicated in skins should be avoided. Or maybe put them in a different recipe so the others install that extra package?
Edited by littlesat, 21 December 2023 - 10:05.

all depends how other distros will agree to do it...If they dont agree to additional packages or in the base code then we have to stick it in the skin.

But since its only the BoxLogo renderer maybe it can be included in the logos package (that currently exists in ViX for example. In ViX it is enigma2-boxlogos package).

Edited by DimitarCC, 21 December 2023 - 10:37.

Sounds we need a different recipe here… at least I think you understand having renderers and converters dedicated in skins should be avoided. Or maybe put them in a different recipe so the others install that extra package?

As the Renderer goes with the logos it should be packaged with the logos. That way downloading the logos makes the Renderer available. And without the logos the Renderer is not needed so should not be embedded in enigma core code.

As the Renderer goes with the logos it should be packaged with the logos. That way downloading the logos makes the Renderer available. And without the logos the Renderer is not needed so should not be embedded in enigma core code.

 

This is a good weighted work-a-round (as long the skin still works when the it's not there).

Edited by littlesat, 21 December 2023 - 12:43.

The skin will work even if the renderer is not there. But it will not show any logos in this case.

This is indeed how it should respond.

The skin will work even if the renderer is not there. But it will not show any logos in this case.

Edited by littlesat, 21 December 2023 - 14:29.

Btw we need to add the recipe for the box logo’s…