2057 replies to this topic

[WanWizard]

Btw, there are different errors, depending on where it crashes. This is a different one:

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/Addons/ColorButtonsSequence.py", line 52, in buildEntry
    if len(sequence) == 0:
SystemError: <built-in function len> returned a result with an exception set
TypeError: 'float' object cannot be interpreted as an integer

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/Addons/ColorButtonsSequence.py", line 52, in buildEntry
    if len(sequence) == 0:
SystemError: <built-in function len> returned a result with an exception set
TypeError: 'float' object cannot be interpreted as an integer

The above exception was the direct cause of the following exception:

SystemError: _PyEval_EvalFrameDefault returned a result with an exception set
[ePyObject] (CallObject(<bound method InfoBarUnhandledKey.checkUnused of <class 'Screens.InfoBar.InfoBar'>>,()) failed)

[Schrotty74]

Its in the feed of nightly/develop image. E2-DarkOS.

I am on Dev Build but dont see it.

[littlesat]

It is there believe me. Please note you need to install it first via green button plug-in selection screen.

Edited by littlesat, 10 May 2024 - 15:44.

[Schrotty74]

It is there believe me. Please note you need to install it first via green button plug-in selection screen.

I am in Plugins and thene Skins thene see mamy Skins but not this.

[Huevos]

 

I have no idea what can cause this.....Since you said was fixed what made it come back?

 

I have absolutely no idea.

 

Huevos mentioned the Python 3.10 issues, and I've implemented those workarounds here: https://github.com/O...39d786a15709080

 

which fixed it. I rebased with develop yesterday, so this is the only difference between kirkstone and evelop, but now it's back?

 

Where are the other 2 commits? That is just the python.c commit.

 

https://github.com/O...a79660e5b7fbb07
https://github.com/O...86649715fd41312
 

Edited by Huevos, 10 May 2024 - 16:16.

[Schrotty74]

A other user say also its not on the feed. I have the UNO 4K SE. Can you upload please the latest build.

[DimitarCC]

The skin can not be installed manually since it have per box dependencies. So it must be installed via plugins.
And it is there. The name is e2-darkos however.

[Schrotty74]

The skin can not be installed manually since it have per box dependencies. So it must be installed via plugins.
And it is there. The name is e2-darkos however.

I dont know why i not see and other user also. I am on latest 9.1.

Edited by Schrotty74, 10 May 2024 - 17:41.

[DimitarCC]

Are you sure you are on nightly?
Show the about screen

[littlesat]

9.1 does not exist. Can’t be a real openpli and the skin starts with e2

[Schrotty74]

Are you sure you are on nightly?
Show the about screen

Yes

[DimitarCC]

Run online update.... Maybe will show up.... I dont know i have it on my box...

[Schrotty74]

I have it and its not show.

Edited by Schrotty74, 10 May 2024 - 18:31.

[kamaxx]

@DimitarCC,

 

 

Yes, indeed!

 

I have faced some times that problem and I tried last dev image now.

I can not see e2-darkos skin.

[DimitarCC]

Then it is something with the build. @WanWizard or @littlesat may need to check.

[catastrofus]

Indeed, it's not in the feed. After updating my box (and rebooted it) and removing darkos skin I rebooted my box (again) to install darkos but this skin isn't visible in the feed.

 

 

Attached Files

•  dark.jpg   139.6KB   3 downloads

[DimitarCC]

Ok. @WanWizard @littlesat please check.

[WanWizard]

There were some aborted build runs earlier, due to changes to edid-decode.

 

The current build run looks ok sofar but won't be ready until early tomorrow morning.

[Huevos]

 

 

I have no idea what can cause this.....Since you said was fixed what made it come back?

 

I have absolutely no idea.

 

Huevos mentioned the Python 3.10 issues, and I've implemented those workarounds here: https://github.com/O...39d786a15709080

 

which fixed it. I rebased with develop yesterday, so this is the only difference between kirkstone and evelop, but now it's back?

 

Where are the other 2 commits? That is just the python.c commit.

 

https://github.com/O...a79660e5b7fbb07
https://github.com/O...86649715fd41312
 

 

@WanWizard, just in case you missed this.

[WanWizard]

Eh... yes, completely. Thanks!

 

btw, I wonder why nobody else has reported this, I know there are others testing kirkstone with this skin (appearently the standard skin doesn't have this problem).

 

edit: I can confirm these commits fixed the issue. Thanks again.

Edited by WanWizard, 11 May 2024 - 12:17.