Findings after 3 days

[Pale-Rider]

Going by that crash log it's pointing towards a keymap file error, you should be able to open the keymap file in a compatible text reader like notepad++ or GEDIT to check it.

just for comparison sake, this is a copy of the keymap.xml file from my Solo2 running OpenViX Zeus build 003 ( located in /usr/share/enigma2/ ), open it in a compatible text editor such as Gedit or notepad++. ( dont go messing with this file unless your prepared for a BSoD or two, and always back up the original just to be safe ).

[el bandido]

We have sent blindscan crash logs to OpenATv and to OpenVix several times over a couple month period. I guess the reason it is not fixed is because the key error is not as easy to fix as altering or changing the key file in the enigma shares folder?

To fully understand the keymap problem, go to the blindscan plugin folder located at: /usr/lib/enigma2/python/Plugins/SystemPlugins/Blindscan
Decompile the pyo files in that folder and see what it calls for. Doing this will give you a better understanding of what the keymap error is and what is needed to fix it. EB

[Pale-Rider]

We have sent blindscan crash logs to OpenATv and to OpenVix several times over a couple month period. I guess the reason it is not fixed is because the key error is not as easy to fix as altering or changing the key file in the enigma shares folder?

To fully understand the keymap problem, go to the blindscan plugin folder located at: /usr/lib/enigma2/python/Plugins/SystemPlugins/Blindscan
Decompile the pyo files in that folder and see what it calls for. Doing this will give you a better understanding of what the keymap error is and what is needed to fix it. EB

In our defense we ( ViX ) are a very small team of amateurs, we have one primary coder who basically created and continues to updated and work on the image ( Andy black ) and the rest of us are testers or dabble here and there. Blindscan on the other hand is pretty much the sole responsibility of one guy ( Huevos ) who is a full time satellite installer in spain, so his time is very limited.

The best thing to do when requesting features or fixes is to make a thread on the forum it self clearly explaining what your trying to achieve, with crash logs, debug logs and every thing else you can thing of. and last but not least, I cant speak for ATV but ViX have pretty much been concentrating on getting Zeus ready for the past 5 months or so, so unless the crash report was something we would class as urgent it would have been put to one side for the time being.

[Pale-Rider]

We have sent blindscan crash logs to OpenATv and to OpenVix several times over a couple month period. I guess the reason it is not fixed is because the key error is not as easy to fix as altering or changing the key file in the enigma shares folder?

To fully understand the keymap problem, go to the blindscan plugin folder located at: /usr/lib/enigma2/python/Plugins/SystemPlugins/Blindscan
Decompile the pyo files in that folder and see what it calls for. Doing this will give you a better understanding of what the keymap error is and what is needed to fix it. EB

One last thing, there is no need to go through the hassle of decompiling .pyo files here, you can get the .py files directly from our GIT.

https://github.com/oe-alliance/oe-alliance-plugins/tree/master/Blindscan

https://github.com/oe-alliance/oe-alliance-plugins/commits/master/Blindscan

If you have comments, questions or require fixes for certain issues, you can leave them directly in the GIT for the specific plugin / project and it's coder will be notified directly.