Green Screen of Death

Just got a report at Satguys of another person that owns 2 regular Mio 4k receivers, and they just both crashed with this error. I've asked them to report over here, but that's up to them.
 
I just received a similar report from a OS Mio 4K eBay customer that received a software error screen last evening and is rebooting. Asked him to post the STB log.
 
It seems possibly to be the weatherMsn plugin causing the crash. I removed the weather plugin with remove plugins menu and also deleted the weatherMsn folder from usr/lib/enigma2/python/plugins/Extensions. No problem now with GlamourAuraFHD skin.
 
User at Satguys reports that simply removing the internet cable allows him to boot up normally. IF he plugs in the ethernet cable, it immediately crashes with the greenscreen again.

So, a person could remove internet access, switch to a different skin, and/or remove the weatherMsn plugin, and perhaps avoid having to reflash from scratch.

At least until we have a fix.
 
MikeB said:
User at Satguys reports that simply removing the internet cable allows him to boot up normally. IF he plugs in the ethernet cable, it immediately crashes with the greenscreen again.

So, a person could remove internet access, switch to a different skin, and/or remove the weatherMsn plugin, and perhaps avoid having to reflash from scratch.

At least until we have a fix.
Click to expand...

Confirmed That works. When crash occurs remove internet then unplug power and re power up. boots normal.
 
Deleted only the MSN Weather plugin and connected to ethernet. After a while, the error occurred again.

With the MSN Weather plugin and Glamour Aura skin removed then connected to ethernet, the STB remains stable.
 
Titanium said:
Deleted only the MSN Weather plugin and connected to ethernet. After a while, the error occurred again.

With the MSN Weather plugin and Glamour Aura skin removed then connected to ethernet, the STB remains stable.
Click to expand...

Yeah the weatherMsn folder at usr/lib/enigma2/python/plugins/Extensions has to be deleted. Seems just uninstalling with remove plugin (red button) didn't really uninstall it. I used dream-explorer plugin to delete that folder.
 
Currently the feeds and all online images have been deleted. Doing this was probably over-kill, but it was done before a lot of information about this problem existed.

The last updates for TNAP would have been a couple of weeks ago. Nothing has been added or changed to the public TNAP since that time.
The Glamour skin was last updated in April 2021 according to the information at Github. So the image was updated a couple weeks ago, and the Glamour skin around a month ago. But the rebooting or bootlooping started around 24 hours ago.... Go figure...

I have said this before but it needs to be known: We do not push updates or anonymously send things to the receiver. On the surface, it looks like a bad update, but the image was last modified some two weeks ago, and the Glamour skin modified a couple weeks before that (April).

It would be a good idea to look at what feeds from the internet and what other plugins (bitrate, weather, etc.) the Glamour skin uses. Nothing is certain, but it seems to be something that is feeding or getting information from the Internet.

Something that is easy to do will be to build test images with some items missing such as the weather plugin. The problem needs to be narrowed down, then pinpointed and fixed. Unfortunately it might take some time to do this.
 
For anyone interested, here is the error:
IOError: [Errno 22] Invalid argument
Traceback (most recent call last):
File "/usr/lib/enigma2/python/mytest.py", line 211, in processDelay
callback(*retval)
File "/usr/lib/enigma2/python/Tools/BoundFunction.py", line 9, in __call__
File "/usr/lib/enigma2/python/mytest.py", line 464, in runNextScreen
session.openWithCallback(boundFunction(runNextScreen, session, screensToRun[1:]), screen, *args)
File "/usr/lib/enigma2/python/mytest.py", line 290, in openWithCallback
dlg = self.open(screen, *arguments, **kwargs)
File "/usr/lib/enigma2/python/mytest.py", line 300, in open
dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
File "/usr/lib/enigma2/python/mytest.py", line 243, in instantiateDialog
return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
File "/usr/lib/enigma2/python/mytest.py", line 260, in doInstantiateDialog
dlg = screen(self, *arguments, **kwargs)
File "/usr/lib/enigma2/python/Screens/InfoBar.py", line 66, in __init__
File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 268, in __init__
File "/usr/lib/enigma2/python/Screens/Screen.py", line 131, in show
File "/usr/lib/enigma2/python/Components/Renderer/Renderer.py", line 10, in onShow
File "/usr/lib/enigma2/python/Components/Element.py", line 99, in setSuspend
File "/usr/lib/enigma2/python/Components/Element.py", line 104, in checkSuspend
File "/usr/lib/enigma2/python/Components/Element.py", line 94, in setSuspend
File "/usr/lib/enigma2/python/Components/Converter/Poll.py", line 32, in doSuspend
File "/usr/lib/enigma2/python/Components/Converter/Poll.py", line 25, in poll
File "/usr/lib/enigma2/python/Components/Converter/GlamMSNWeather.py", line 2315, in changed
Converter.changed(self, (self.CHANGED_POLL,))
File "/usr/lib/enigma2/python/Components/Element.py", line 86, in changed
File "/usr/lib/enigma2/python/Tools/CList.py", line 7, in __call__
File "/usr/lib/enigma2/python/Components/Renderer/GlamPiconUni.py", line 39, in changed
sname = self.source.text
File "/usr/lib/enigma2/python/Components/Element.py", line 15, in wrapper
File "/usr/lib/enigma2/python/Components/Converter/GlamMSNWeather.py", line 827, in getText
BETA = math.acos((math.cos(90.35 * DEG2RAD) - math.sin(DEC * DEG2RAD) * math.sin(lat * DEG2RAD)) // (math.cos(DEC * DEG2RAD) * math.cos(lat * DEG2RAD))) * RAD2DEG # hour angle
ValueError: math domain error
Click to expand...

It looks like the program is computing a value for BETA and it is coming back as 0 or as a negative number. So it throws the IOError and tries to restart.
The million dollar question is why did the BETA calculation suddenly start returning an illegal value and what can we do to go around it or fix it?
 
Looks like a possible fix. (See screencap)

glamour-fix_20210521000031.webp

Should be able to put some test images out tomorrow. If it works for me, then hopefully it will work for everyone.
 
TNAP images were uploaded to this site at the end of 2020.
The 2020 TNAP4 MIO+ images are here:https://legitfta.com/forum/showthread.php?26985-TNAP-4-Images-for-OSMIO4K-20201221
These 2020 images have the exact same bootloop issue for me. So it looks like the data that the weather plugin grabs changed which in turn caused the IOError.

I will leave the Test Glamour skin running for the rest of the night and will check it in the AM. Should be pretty obvious if it is not working.
 
How about just removing the Weather plugin from the images entirely? I really don't see any need to check weather on my FTA satellite receiver. I get mine from Accuweather, and 1Weather on my phone.
 
Last edited:
The weather is in the skins because some users wanted it. Personally I use PLi HD night skin for simplicity. Different users have different preferences.

If we remove the weather plugin, then there will be holes or blank spaces in more than one skin. So to remove the weather plugin correctly, then we would need to modify every skin that uses the weather plugin and remove the blank spaces for the weather displays.

Then what do we do the next time there is a problem with a plugin or even a part of the image? Do we just remove it too???

This weather plugin issue will be fixed.

BTW, This is not just a TNAP problem. Other images that use the same converter and display the weather are affected by this.
 
A hopefully permanent fix will be applied tonight on my Github!
And please next time I will really appreciate it if anyone with a problem contacts me on my email, it will certainly help issues get fixed sooner!
 
The feeds are up with a Glamour skin update that seems to solve the issue.

Installing a single .ipk file may be easier, and does not require an internet connection to the receiver.

Any TNAP image that is less than 6 months old may have this issue. The feeds will be updated and rebuilt. New images will be made available, but these things take time.

For tonight and until things can be completly corrected, you may update online using the receiver menus OR use telnet with this one line command: opkg update && opkg upgrade && reboot

As an alternative, you can install the attached Glamour skin plugin which is an .ipk file.
To install the attached plugin, download the plugin and install it on a Known To Be Good usb stick, insert the usb stick into the receiver while watching a tv channel (with or without a signal), then follow onscreen instructions.
 

Attachments

I just downloaded the GlamourAura fixed skin, and re-installed the WeatherMSN plugin. I just started another full backup right now, and then I'll switch back to the GlamourAura skin, and see what happens. I'll re-post results.


Ok, backup finished, I switched back to the GlamourAura skin after previously downloading the fix through the feeds, and it rebooted. Everything now appears to be working perfectly once again!

I love that particular skin, and I give kudos and thanks to MCelliotG for a quick fix, and just keeping this maintained in general. I'm sure it's a LOT of work to do so. Also, kudos to El Bandido, as I also really appreciate his expertise, and help in general.
 
Back
Top