Jump to content


ims

Member Since 3 Feb 2007
Offline Last Active Today, 13:54
*****

Posts I've Made

In Topic: Analog clock (2.0) green screen in open PLi 9.0

Yesterday, 20:24

	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.


In Topic: Analog clock (2.0) green screen in open PLi 9.0

Yesterday, 19:17

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.


In Topic: Analog clock (2.0) green screen in open PLi 9.0

Yesterday, 18:46

? Could you put here crash log ?


In Topic: Analog clock (2.0) green screen in open PLi 9.0

Yesterday, 14:19

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


In Topic: Analog clock (2.0) green screen in open PLi 9.0

Yesterday, 11:56

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) ?