Vu+ Duo 4K Spontaneously goes into deep standby

[bird]

For a few weeks now my VU+ Duo 4K has been going into deep standby at 10:00 am, I can only turn it back on by restarting it with webif or by turning the power off and on again. It no longer responds to the remote control. Before this started the display went black for a while and then lit up again but now it stays black, this was also always at 10:00 am. I have checked all the timer settings and can't find anything abnormal. Is anyone familiar with this phenomenon? Help would be very welcome because it is an annoying problem in connection with planned recordings.
Greetings, bird

[s3n0]

Debug log ? - viewtopic.php?t=45829#p389750

[bird]

Here the crash log

20250407-100118-enigma2-crash.log

(76.99 KiB) 11-mal heruntergeladen

[s3n0]

Hi.

There's more. It starts with this problem, the non-existent Cover component:

Code: Alles auswählen

14:08:37.4596   File "/usr/lib/enigma2/python/skin.py", line 2172, in processWidget
14:08:37.4597 KeyError: 'Cover'

Then the same thing is repeated several times - for MoviePlayer:

Code: Alles auswählen

20:29:53.3553 Traceback (most recent call last):
20:29:53.3554   File "/usr/lib/enigma2/python/skin.py", line 2309, in processScreen
20:29:53.3554   File "/usr/lib/enigma2/python/skin.py", line 2174, in processWidget
20:29:53.3556 skin.SkinError: [Skin] Error: Component with name 'Cover' was not found in skin of screen 'MoviePlayer'!
20:29:53.3646 Traceback (most recent call last):
20:29:53.3647   File "/usr/lib/enigma2/python/skin.py", line 2172, in processWidget
20:29:53.3647 KeyError: 'Cover'

Eventually the whole system will collapse:

Code: Alles auswählen

10:01:18.0072 Traceback (most recent call last):
10:01:18.0136   File "/home/oe1/atv751arm/build-enviroment/builds/openatv/release/h9se/tmp/work/all-oe-linux/enigma2-plugin-extensions-bouquetmakerxtream/git/image/usr/lib/enigma2/python/Plugins/Extensions/BouquetMakerXtream/update.py", line 777, in loadSeries
10:01:18.0219   File "/home/oe1/atv751arm/build-enviroment/builds/openatv/release/h9se/tmp/work/all-oe-linux/enigma2-plugin-extensions-bouquetmakerxtream/git/image/usr/lib/enigma2/python/Plugins/Extensions/BouquetMakerXtream/globalfunctions.py", line 176, in downloadUrlMulti
10:01:18.0222 MemoryError
10:01:18.0223 [ePyObject] (PyObject_CallObject(<bound method BmxUpdate.loadSeries of <class 'Plugins.Extensions.BouquetMakerXtream.update.BmxUpdate'>>,()) failed)

I probably can't help you with this. Some developer from the OpenATV team has to look into it.

Also, write whether you installed something yourself into OpenATV 7.5.1 or whether you are using pure OpenATV 7.5.1 downloaded from the internet.

According to the update, it is the current OpenATV build - the one you are using.

However... similar errors can occur when you don't update the OpenATV image for a long time and after, for example, 1 month, you decide to run the update. In such a case, in the meantime, there might have been an update to the "Cover" component, which will be missing from your set-top box. After a late update, this older thing will unfortunately not be added to your OpenATV and will be missing. Of course, I don't know whether this is a component falling under the OpenATV source code (skin) or whether this component belongs more to some MoviePlayer plugin (installed by you? or is it also part of OpenATV?).

[bird]

Thanks in advance for your help, I always do updates when there are any, so that can't be the problem.
Hopefully someone from the developers of the software can help me;
Greetings,
bird

[Papi2000]

So sometimes it's better to flash online (and maybe restore, but only if possible{!}). That can heal some small glitches.
If that does not help, you have to flash clean, and reactivate step-by-step the settings manually, until you find the bad setting for your environment.

[s3n0]

Thanks in advance for your help, I always do updates when there are any, so that can't be the problem.
Hopefully someone from the developers of the software can help me;
Greetings,
bird

Well... please, connect to your set-top box via FTP and check for the existence of the file:
"/usr/lib/enigma2/python/Components/Renderer/Cover.pyc"

This file should exist if your OpenATV updates are fine and without any corruption.

However, according to the debug log, this file will be missing from your OpenATV.

If that doesn't work... I recommend doing a complete reflash of the set-top box with the latest OpenATV build downloaded from the internet.

[bird]

@ s3n0 The file you indicated does exist, I will do a complete new installation if it is not resolved.
In any case, thanks for helping me, and also thanks to papi2000
Greetings,
bird

[s3n0]

So then what I wrote applies. You haven't updated OpenATV for a very long time. However, in the meantime, an important update need arose. Later it was lost. These updates work on the principle of the so-called incremental sequence - often something is just added. So if you don't update for a long time (sometimes 1-2 weeks is a very long time), this can happen.

Theoretically, you could download this one file to your set top box from the internet. You can, for example, use a terminal connection and use the Linux Shell:

Code: Alles auswählen

wget --no-check-certificate -O /usr/lib/enigma2/python/Components/Renderer/Cover.py "https://github.com/openatv/enigma2/raw/refs/heads/master/lib/python/Components/Renderer/Cover.py"

reboot

But it is quite possible that other things will be wrong there as well. So it would be more appropriate to do a complete flash again + perform user settings.

If you update your set top box with OpenATV, you should do so regularly - for example, every week. But regularly - without skipping the weekly update schedule.

[Papi2000]

It was nowhere recommended, to do daily updates.
It was never recommended to do so.
User can do updates. Regularly they are working.
After mayor changes for the image in combination to the user installed plugins and individual user settups, it may fail.
In those cases, it may help to flash new, and restore all settings.
In some cases, even that fails. Then it will be necessary to flash clean without other storage devices in/at the box, and set up manually new. It can be necessary, to omit bad plugins permanently no longer working.