577 replies to this topic

[bujars]

Hello, i installed new 9.0 in mu v+ uno se 4k, but i have problem when i try to update, when i try tu change something, enigma crash every time,

This is the crash log

 

Traceback (most recent call last):

  File "/usr/lib/enigma2/python/Components/Opkg.py", line 182, in cmdFinished

  File "/usr/lib/enigma2/python/Components/Opkg.py", line 242, in callCallbacks

  File "/usr/lib/enigma2/python/Screens/SoftwareUpdate.py", line 232, in opkgCallback

  File "/usr/lib/enigma2/python/StartEnigma.py", line 302, in openWithCallback

    dlg = self.open(screen, *arguments, **kwargs)

  File "/usr/lib/enigma2/python/StartEnigma.py", line 312, in open

    dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)

  File "/usr/lib/enigma2/python/StartEnigma.py", line 255, in instantiateDialog

    return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)

  File "/usr/lib/enigma2/python/StartEnigma.py", line 279, in doInstantiateDialog

    dlg.applySkin()

  File "/usr/lib/enigma2/python/Screens/Screen.py", line 240, in applySkin

  File "/usr/lib/enigma2/python/Screens/Screen.py", line 269, in createGUIScreen

  File "skin applet", line 21, in <module>

  File "/usr/lib/enigma2/python/enigma.py", line 1249, in __init__

TypeError: in method 'new_ePoint', argument 1 of type 'int'

[ePyObject] (CallObject(<bound method OpkgComponent.cmdFinished of <Components.Opkg.OpkgComponent object at 0xb0a0bc58>>,(0,)) failed)

[WanWizard]

Using a non-default skin?

[bujars]

i use this enigma2-plugin-skins-mx-hq7-pli-v2_1.0_all

[WanWizard]

Problem is that most likely somewhere a calculation is made for a coordinate on screen, which have to be integer values. Python 2 converts fractions automatically, in Python 3 either conversion has to be done, or an integer division has to be used instead.

 

This suggests the skin is not Python 3 compatible,

 

Revert back to the original skin, and see if that fixes the problem. If so, contact the maker of that skin.

 

[mrvica]

skin applets are in python and can be found in some skins for ChoiceBox or MessageBox(Simple), if you delete i.e ChoiceBox or MessageBox screen corresponding are used from skin_default.xml and skin should restart, look after in your skin

 

<screen name="MessageBox" position="center,140" size="800,10" title="Message">

    <widget name="text" position="80,8" size="710,484" font="Regular;22" />

    <widget name="ErrorPixmap" pixmap="icons/input_error.png" alphatest="blend" position="10,5" size="53,53" />

    <widget name="QuestionPixmap" pixmap="icons/input_question.png" alphatest="blend" position="10,5" size="53,53" />

    <widget name="InfoPixmap" pixmap="icons/input_info.png" alphatest="blend" position="10,5" size="53,53" />

    <widget name="list" position="15,504" itemHeight="32" size="770,196" scrollbarMode="showOnDemand" />

    <applet type="onLayoutFinish">

from enigma import eSize, ePoint

orgwidth = self.instance.size().width()

orgpos = self.instance.position()

.........

.........

</applet>

and try to correct it

[40H3X]

 

However i'm surprised that py is 3.9.9 which is a wee bit old - is there any reason you're running this version?

are you planning to have it upgraded in future release?

 

Yes, the reason is we use whatever version is used in the OpenEmbedded version we use.

 

Normally with a major release upgrade, we also upgrade the OE version, but this time we didn't because of the amount of work of upgrading to py3.

 

There is an OE upgrade to either Kirkstone or Nanbield in the planning for OpenPLi 10.

 

( having said that, unless you're a bleeding edge developer, the version used is not very relevant )

 

Slight correction and just for the record   with OpenPLi 9 to a higher version of OE. OpenPLi 8 was on Zeus with OpenPLi 9 we went to Hardknott 

[WanWizard]

Slight correction and just for the record   with OpenPLi 9 to a higher version of OE. OpenPLi 8 was on Zeus with OpenPLi 9 we went to Hardknott

 

You're absolutely right, I stand corrected.

[void]

If you install 9.0 on a Duo 4K from another image no SSH is available. Of course I’ve logged in with telnet and set a pw pricier to try to login with SSH. Upgrading from an older openPLI with backup works.

[WanWizard]

That is standard in every OpenPLi image.

 

SSH is disabled until you set a password. This is to prevent the box from being hijacked if you're stupid enough to connect it directly to the internet, or use SSH port forwarding ( believe me, such people exist ).

[void]

I know. That’s why I said that I’ve set a password during my Telnet session. But I was still unable to connect.

[void]

With 8 openPLI image same procedure (login by telnet, set pw and login with ssh) worked.

[WanWizard]

Then I misunderstood. I can't say I have ever observed this, but I'll flash my test box now and see.

[WanWizard]

I can't confirm this.

 

Flashed the box, answered "no" when prompted for a restore, selected language and output, and aborted the setup wizard.

 

Connected with telnet, set a password, logged out again. Connected with SSH, logged in with root and the password I set. No problem.

[40H3X]

Of course same here, telnet has default no password, if you want to login SSH one has to be set

[void]

I mean a fresh install. Not the Upgrade option from the Menue. I was on VTi before…

[WanWizard]

Which I did:

 

I can't confirm this.

 

Flashed the box, answered "no" when prompted for a restore, selected language and output, and aborted the setup wizard.

 

Connected with telnet, set a password, logged out again. Connected with SSH, logged in with root and the password I set. No problem.

 

[alabama]

Hello OpenPLi Team,
please fix the Serienrecorder extension in the feed of OpenPLi 9.0.

The correct installation-folder must be usr/lib/enigma2/python/Plugins/Extensions/serienrecorder not
usr/lib/enigma2/python/Plugins/Extensions/SerienRecorder.

Thank you for the wonderful image

Edited by alabama, 29 October 2023 - 20:00.

[WanWizard]

Why? When has that changed?

 

It is highly unusual to use all lower case, and also, unless the plugin does something it is not supposed to (i.e. accessing its own code directory), the name of the directory is irrelevant?

 

edit:

 

I see it already, crap code, hardcoded paths all over the place

[WanWizard]

Should be fixed now. You might have to uninstall / install, not sure it will be seen as an update.

[alabama]

@WanWizard:

Thank you very much

I will test it an give feedback.