Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! 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 £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[OS-mio+] key ButtonSetup and error with debug background

norhap

Member
Joined
Jul 13, 2011
Messages
189
Reaction score
0
Points
16
Age
54
Hi guys, I debuted the current image, and I'm having a rather annoying background error, it repeats every 120 sec approx.
Code:
<  1888.380> Unhandled error in Deferred:
<  1888.380>
<  1918.383> Unhandled error in Deferred:
<  1918.383>
<  1948.382> Unhandled error in Deferred:
<  1948.382>
<  1978.383> Unhandled error in Deferred:
<  1978.384>
<  2008.383> Unhandled error in Deferred:
==================================================

more.....buttonsetup doesn't obey me, example:

If I assign green key to foreca plugin it does not run:
Code:
<1707.032> [InfoBarGenerics] KEY: 399 GREEN
<1707.217> [eInputDeviceInit] 0 18f 1
<1707.218> [InfoBarGenerics] KEY: 399 GREEN

regards norhap.
 
Thanks will have a look - not sure I have seen that in debug log but will check
 
Something going on here ......... I do not get this error (I always run with debug) and I have searched debug logs over a week.

with box edision?....
I had the error with my git image, seeing this and thinking that it was a problem of my enigma2, I decided to install the official openvix image and the problem persisted.

... and I can use button setup for plugins and it works - there are symlinks between the 2 libraries(lib and lib64), so would expect it to work

It has been impossible to be able to map the keys with ButtonSetup, this solved it for me at once.

It was to bring this commit by captain to my git and matter resolved:

https://github.com/openatv/enigma2/...ab4e6ed#diff-a3ad8005c8c13cd0ae85f6f9e31f5c39
 
I have an Edision 4K plus and nothing in debug logs.
 
with box edision?....
I had the error with my git image, seeing this and thinking that it was a problem of my enigma2, I decided to install the official openvix image and the problem persisted.



It has been impossible to be able to map the keys with ButtonSetup, this solved it for me at once.

It was to bring this commit by captain to my git and matter resolved:

https://github.com/openatv/enigma2/...ab4e6ed#diff-a3ad8005c8c13cd0ae85f6f9e31f5c39
OK - actually executed the button(!) and you are correct needs the code change!

However do not get the „unhandled“ error
 
< 124.577> Unhandled error in Deferred:
< 124.578>
< 125.391> [Avahi] watch activated: 0x1
< 125.391> [Avahi] avahi_timeout_update
< 125.391> [Avahi] timeout elapsed
< 125.391> [Avahi] avahi_timeout_update

test image oficial 0.11
image slot 2
no restore backup. not config.

Use this order please:
Code:
init 4&& sleep 10&& ENIGMA_DEBUG_LVL=4 enigma2
 
test image oficial 0.11
image slot 2
no restore backup. not config.

Use this order please:
Code:
init 4&& sleep 10&& ENIGMA_DEBUG_LVL=4 enigma2

I am running off my own build - but I don‘t get the issue.
Are you using lan or wifi connection??
 
I don't understand how I clearly detect it and you don't.
I use LAN.
 
So I guess my conclusion is that either the issue is cleared up on OEA 4.4 (which I currently build on) or you have a usb device attached to the receiver that is throwing up a bus error
 
yes, problem with my USB stick.

root@osmio4kplus:~# fsck.vfat /dev/sda1
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.

thanks.
 
yes, problem with my USB stick.

root@osmio4kplus:~# fsck.vfat /dev/sda1
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.

thanks.

Although to be honest with the quality of some usb sticks this is a likely issue - should be handled better
 
I have deleted a corrupt bit in my vfat partition, but the problem still remains, as soon as I return to the official lcd.py openvix the problem arises.

something similar was manifested in Lcd.py of openvision, I had to make the commit that you already know to fix it .... it does not seem very coincidental to me that in ambox .py is having these strangers.
 

OpenViX Feeds Status

Back
Top