Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Ultimo] Crashloop at boot after online update to Apollo 30

  • Thread starter Thread starter jukkal
  • Start date Start date
J

jukkal

Guest
As I didn't see any warning about needing to flash when updating from Apollo 29 to 30, I used online update for the process.
After updating and booting, first the infobar at the bottom of the screen flashed quickly like it usually does, but then instead of the tv picture, I just saw a crash report and enigma2 started rebooting. And never got further than that, always rebooted when it should have begun showing the tv picture.
I had made a full backup of the Apollo 29 image I used before the update, so I unpacked it to the usb stick and flashed, but the same happened with it.
Luckily I also had a full image backup of the Apollo 24 build, which was the last one before the qwerty keyboard stopped working, so the next I unpacked THAT to the usb stick, reflashed again, and now the Ultimo works again, back with Apollo 24.

During the crash reboot loop I took a photograph of the TV screen showing the error messages, and now that I have more than 10 seconds before restart, I can see it shows "Component: WebAdmin". I remember trying to install WebAdmin plugin at some point, but got some error message.
P9081422.webp
Do you need the crash logs too, or does the screenshot contain all information necessary?

Does build 30 fix the bug with the Ultimo qwerty keyboard? Any build after Apollo 24 that I have tried, hasn't reacted to the qwerty keys any way, no matter which way I have the text support setting in the remote control code setup screen. If there is no fix for this in build 30, I guess I'd rather wait for 31..
 
Have you tried a fresh flash and setup of 030?
Also, yes we need crashlogs please.

No, I just used the online update because I didn't see here any warning that flashing would be needed. Here are the logs.
 

Attachments

Try a fresh flash and setup, do not restore. Once setup, install EPG Refresh plugin and reboot.
I've just had this same problem on Apollo 041.
Installed several plugins - restarted GUI and ended up in a loop.
Had to reflash.
Added in the new plugins I was adding one at a time, and when it got to webadmin I ended up in this forever-loop again.
So reflashed a second time and this time added the new (to me) plugins without adding webadmin.

I've now installed EPGRefresh by hand first. The start-up loop has now gone. But if WebAdmin needs EPGRefresh then shouldn't it have it as a pre-requisite so that it gets installed if not present?

And WebAdmin still fails to start, as there is no module called Screenpage. Looks like this is meant to be in WebInterface (probably in /usr/lib/enigma2/python/Plugins/Extensions/WebInterface/WebChilds), but it isn't.
 
A failed plugin. Should not be available in plugin list
 
A failed plugin. Should not be available in plugin list
No, it isn't shown, but everytime you go to the Plugins page you get a message saying that it isn't available.
The relevant thing here is it not specifying dependencies which it needs and which exist, and it also requiring something which does not seem to exist at all!

And I've just had another plugin oddity. I removed the SeriesPlugin, and the opkg info no longer shows it,. but all of the files were left in place, so it produces an error message (no Licence) when I bring up the Plugins page. (Removing the SeriesPlugin directory from under Extensions by hand has solved that).
 
Badly coded plugins so.
Atleast you know now not to install them.
We can't possibly test all combinations of all plugins on all boxes.
 
We can't possibly test all combinations of all plugins on all boxes.
I know.
But is there any official place where such issues with individual plugins can be reported, so that:
  • the maintainer(s) can potentially fix them
  • others can see the issues and hence know what to expect
 

OpenViX Feeds Status

Back
Top