20 replies to this topic

[Belgianviking]

Have updated OpenPLI from 8.3 to 9.0 (edition 04 03 2024 for all boxes). Am running 1 Octagon SF 8008 and 2 Zgemma H9 Twin. All flashing via USB. After flashing said yes to perform auto update (backed up from OpenPLI 8.3 mars 2023 edition) and got a green screen caused by the extension Analog clock (as the text from the green screen indicated).

After reflashing the boxes with OpenPLI 9.0 I downloaded the plugins I needed except Analog Clock 2.0 (did mot want to get a new green screen issue again)  and all was fine. What might cause the green screen with this analaog clock exension? any solution you can recommend to solve that issue with the Analog clock?.

[WanWizard]

We won't know until you post the crash log here, but it is probably because that plugin is no longer compatible, OpenPLi 9 (and most other images) switched to Pyhton v3 because v2 has been end of life for a while.

[ims]

Have updated OpenPLI from 8.3 to 9.0 (edition 04 03 2024 for all boxes). Am running 1 Octagon SF 8008 and 2 Zgemma H9 Twin. All flashing via USB. After flashing said yes to perform auto update (backed up from OpenPLI 8.3 mars 2023 edition) and got a green screen caused by the extension Analog clock (as the text from the green screen indicated).

After reflashing the boxes with OpenPLI 9.0 I downloaded the plugins I needed except Analog Clock 2.0 (did mot want to get a new green screen issue again)  and all was fine. What might cause the green screen with this analaog clock exension? any solution you can recommend to solve that issue with the Analog clock?.

Permanent Analog Clok or which plugin ? Permanent Analog Clock is compatible and I am using it on all my boxes. Install it and after green screen it should work well...

[Belgianviking]

Hi IMS, thanks for our post. Do you mean that after I had a green screen the first time on ALL MY BOXES the Permanent Analog Clock will work fine when re-installed a second time although according to a Core Member this extenson is not compatible with Pyhton V3?

[ims]

Hi IMS, thanks for our post. Do you mean that after I had a green screen the first time on ALL MY BOXES the Permanent Analog Clock will work fine when re-installed a second time although according to a Core Member this extenson is not compatible with Pyhton V3?

Sometimes, in a clean installation (without an existing backup of configuration), it happens that an issue arises upon the first launch plugin. Subsequent launches work fine, even after reinstalling the box (with backup). I haven't had time to address it.

[littlesat]

In both the analogue clock as the permanent clock there are issues with the analogue part that you have float/integer issues I thing a lot odd / need to replaced by //… so issues with py2->py3 adaption.

[ims]

In both the analogue clock as the permanent clock there are issues with the analogue part that you have float/integer issues I thing a lot odd / need to replaced by //… so issues with py2->py3 adaption.

 

FYI - there are both version on E2OpenPlugins, for py2 (master) and py3 (python3)

Edited by ims, 27 March 2024 - 23:14.

[littlesat]

The permanent clock has also an analogue mode and there indeed some py2->py3 stuff is forgotten. The analogue clock has a bug that after an install you will get gsod which should be resolved after a restart.

Edited by littlesat, 28 March 2024 - 07:52.

[ims]

The permanent clock has also an analogue mode and there indeed some py2->py3 stuff is forgotten. The analogue clock has a bug that after an install you will get gsod which should be resolved after a restart.

... and after 2nd run is solved itself ? No, this bug after 1st install on clear flash (without setting) was time to time under py2 too. I had not time looking for it. I think, it is some race between autorun plugin and not existing it's config value in this time on first run.

Edited by ims, 28 March 2024 - 08:05.

[Belgianviking]

Hi All, many thanks for all the usefull posts and comments. Just one question to core members: is there any chance that  these Pyhton 3 bug related issues might be resolved one day?

[ims]

Hi All, many thanks for all the usefull posts and comments. Just one question to core members: is there any chance that  these Pyhton 3 bug related issues might be resolved one day?

It is not py3 bug. When will be time, I will see on it, but put here error log. I cannot simulate it under 9.0 and under develop too.

 

And works it for you now or no (permanent analog clock) ?

Edited by ims, 28 March 2024 - 12:25.

[ims]

If a GUI restart is performed after installing this plugin, no GSOD will occur in plugin setup after "enable" more.

Edited by ims, 28 March 2024 - 14:20.

[Belgianviking]

Actuallu the GSOD appears when the Extenson (permanent analog clock) is being downloaded. So no I have not tried to re-download this exension and do not see how I can perform a GUI restart when the GSOD in on.

[ims]

? Could you put here crash log ?

Edited by ims, 28 March 2024 - 18:54.

[Dimitrij]

mageissue=openpli 8.3-release %h


Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 77, in action
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 57, in action
  File "/usr/lib/enigma2/python/Components/ConfigList.py", line 228, in keyLeft
  File "/usr/lib/enigma2/python/Plugins/Extensions/AnalogClock/ui.py", line 367, in changedEntry
  File "/usr/lib/enigma2/python/Plugins/Extensions/AnalogClock/ui.py", line 652, in reloadClock
AttributeError: 'NoneType' object has no attribute 'instantiateDialog'
[ePyObject] (CallObject(<bound method NumberActionMap.action of <Components.ActionMap.NumberActionMap instance at 0xadc4b238>>,('SetupActions', 'left')) failed)

Install plugin/open plugin and disable/enable it

[ims]

mageissue=openpli 8.3-release %h


Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 77, in action
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 57, in action
  File "/usr/lib/enigma2/python/Components/ConfigList.py", line 228, in keyLeft
  File "/usr/lib/enigma2/python/Plugins/Extensions/AnalogClock/ui.py", line 367, in changedEntry
  File "/usr/lib/enigma2/python/Plugins/Extensions/AnalogClock/ui.py", line 652, in reloadClock
AttributeError: 'NoneType' object has no attribute 'instantiateDialog'
[ePyObject] (CallObject(<bound method NumberActionMap.action of <Components.ActionMap.NumberActionMap instance at 0xadc4b238>>,('SetupActions', 'left')) failed)

Install plugin/open plugin and disable/enable it

 

Yes, must be restarted gui before first run. But it is not "Actuallu the GSOD appears when the Extenson (permanent analog clock) is being downloaded", as he wrote.

Edited by ims, 28 March 2024 - 19:18.

[Dimitrij]

	def reloadClock(self):
		if not self.dialogAnalogClock:
			self.isShow = False
-			self.dialogAnalogClock = self.session.instantiateDialog(AnalogClockScreen)
+			self.dialogAnalogClock = self.session and self.session.instantiateDialog(AnalogClockScreen)

 

[ims]

	def reloadClock(self):
		if not self.dialogAnalogClock:
			self.isShow = False
-			self.dialogAnalogClock = self.session.instantiateDialog(AnalogClockScreen)
+			self.dialogAnalogClock = self.session and self.session.instantiateDialog(AnalogClockScreen)

That's a solution to the consequence, not the cause. I think I have it sorted out. I need to test it.

[Dimitrij]

 

That's a solution to the consequence, not the cause. I think I have it sorted out. I need to test it.

 

https://github.com/E...be98378d1840e3a

Really

[Belgianviking]

In my case the GSOD appears during the downloading the "Permanent analog clock extension" after flashing to Open PLI 9.0 and saying yes to run the Backup saved when still on OpenPlI 8.3.

Could that be the cause of the issue I have been facing with this extension? In other words if after flashing I do not run the saved Back up made when on OpenPLI 8.3 but perform a fresh downloads of the all the extensions I want  and perform a re-start of the GUI before isntalling the plug in would that solve my issue?