Search results

Try with @KFL ScrollLabel.py https://board.openbh.net/threads/openbh-5-3-009-enigma2-crashlog.4173/page-4#post-21122 I hope @Ev0 make an image update soon

That helps.

I believe this crash is coming because of the console which they still haven't fixed ? Another problem may be the USB stick but the crash is due to the console coding not accepting the skin defined font.

Do not forget You must first install the xtraEvent plugin then skin. ????

Possible. Plugin unknown to me. I have no intention of testing and coding plugins and skins for them . There are hundreds of them.

You have skins for xtraevent on image server green button>>yellow>addons and Feeds Manager>>OpenBH Image skins>>DOWNLOAD xtraEvent skin You can download skins with xtraEvent in name xb skins support baners and xp skins support posters After download and install skin you have to select skin...

xtraEvent v5.2 (with dependent file download) if you have a newly installed image you need to install this file. If you use an image where xtraEvent is already installed you must be sure that everything is deleted/uninstall from the old version, otherwise you cannot install the new version...

xtraEvent v 5.2 with plugin download working

This is not the same skin on your shot We are talking about MX-Slim-Line NP default skin in OBH image. I don't know where you have the image crash.

I really don't know how you get an image crash. Maybe you have activated something that the skin does not support. What buttons do you use / you press to get the crash.

I don't have crash in EventView. Has anyone else tested it?

For me, the download with the plugin works timer download is not working Ask the author of the plugin. This plugin is very problematic.

@mosad Try it. If something doesn't work, you have to ask the author of the plugin to fix it.

@Huevos Forgive me I don't understand again if Regular is declared in emergency skin and in current skin MX_Slim-Line_NP Why does the image crash occur? Once again this is orginal coding used for several years. <screen name="Console" position="center,228" size="1300,700" title="Command...

Thanks, I didn't quite understand. The font is defined in skin.xml Obh default/current skin MX_Slim-Line_NP Regular <fonts> <font filename="tiny.ttf" name="Regular" scale="100"/> and as such it was used for a long time in Console but now it causes an image crash Old coding now it...

So @Ev0 I have to use the console font. Not very nice for this purpose. But now we don't have an image crash. So update skin.xml for default skin MX_Slim-Line_NP @Ev0 Ask the coder to fix this to be able to use the font (name) we want because of this change I would have to update all the...

@Ev0 Ask these image coders if they have better jobs to do than cosmetic changes that only cause skin problems. what did they do they fixed the font name in the Console skin coding So the font must be called Console and not, say, Regular or any another name. WOW :unsure:(y)

I found error in some change in console skin coding.

Then place the skin.xml of that skin here or on our forum.

@Ev0 don't make me crazy :LOL: That file cannot be installed in Duo 4K updated 009 Image Error the same 7031.3973> 23:05:28.6770 Traceback (most recent call last): < 7031.3974> 23:05:28.6771 File "/usr/lib/enigma2/python/Screens/Console.py", line 70, in dataAvail < 7031.3977> 23:05:28.6774...