OpenVIX bug causing crashes

[HeadBanger]

Apologies if this is posted in the wrong section.

I’m running VIX on a VU+ UNO 4K SE and have been really happy with it. I’m running 5.3.034.

I have ordered my favourite bouquet channels 1,2,3,4 etc. and have all my kit controlled by a Harmony remote. I finally got round to programming my favourite channels on the Harmony (basically it presents a screen of channel icons which you press and it simply sends the channel number).

To speed the channel change up I have always programmed three digit channel numbers e.g. channels 1, 10 and 48 are sent as 001, 010 and 048. VIX nearly always crashes if you precede a channel number with zero(s).

Can anyone else confirm same? Can this be logged as a fixable bug please?

Many thanks,

HB

 

[Trial]

Hi,
you better program the Harmony to send without leading 0 but with a following OK/RETURN. This is the way I use it for years now. It does not mean that you did not found a bug but a way to better use the Harmony.

Ralf

 

[HeadBanger]

Thanks Ralf.

I had already removed the zeros on the Harmony commands for now to stop the crashing but will look for the option to add OK at the end as you suggest to speed up the channel change.

I still think it’s a VIX bug though - pressing zero on the remote should not cause it to crash.

HB

 

[twol]

Apologies if this is posted in the wrong section.

I’m running VIX on a VU+ UNO 4K SE and have been really happy with it. I’m running 5.3.034.

I have ordered my favourite bouquet channels 1,2,3,4 etc. and have all my kit controlled by a Harmony remote. I finally got round to programming my favourite channels on the Harmony (basically it presents a screen of channel icons which you press and it simply sends the channel number).

To speed the channel change up I have always programmed three digit channel numbers e.g. channels 1, 10 and 48 are sent as 001, 010 and 048. VIX nearly always crashes if you precede a channel number with zero(s).

Can anyone else confirm same? Can this be logged as a fixable bug please?

Many thanks,

HB

It would help to see the crash log, can you post it

 

[HeadBanger]

I’ve searched but cannot find a crash log. Where do I find it?

Thanks,

Matt

 

[Andy_Hazza]

By default they are stored to /root/logs


Sent from my iPhone using Tapatalk

 

[twol]

If its a crash then you will the log displayed on the TV and the receiver will reboot ... the crash log will also be stored in /root/logs - no need to turn on debug.
However, if not there are you really seeing a crash??

 

[HeadBanger]

It certainly reports that it needs to restart. I pressed zero, zero, one and took a picture as it crashes/restarted but it does not look like I have permission to add it.

HB

 

[abu baniaz]

FTP to the receiver, /home/root/logs
Save crash log to PC,
If you have IPTV, edit it and remove user details
Attach it here (no need to zip).

Guide to attachments on link below. Ignore what is not relevant to you, (we don't need screenshots)
https://www.world-of-satellite.com/showthread.php?44054-How-to-take-screen-shots-How-to-attach-files

 

[HeadBanger]

Here is the crash log.

Many thanks,

HB

 

[ccs]

... no sign of a crash in the logfile (or any key presses) as far as I can see.

 

[HeadBanger]

Sorry I managed to post the wrong one.
This is the correct file.

Is it this?:

< 41003.9809> [ePyObject] (CallObject(<bound method NumberActionMap.action of <Components.ActionMap.NumberActionMap instance at 0x9dd96e68>>,('NumberActions', '0')) failed)

HB

 

[ccs]

Yes - here's a bit more for someone who understands......

< 41002.5429> [eDVBSectionReader] DMX_SET_FILTER pid=5000
< 41002.5436> [huffman] read.. '/usr/share/enigma2/otv_011a0000_0002_0802.dict'
< 41002.5437> [eEPGCache] abort non avail OpenTV EIT reading
< 41002.5437> [eDVBSectionReader] DMX_SET_FILTER pid=57
< 41003.9782> [eInputDeviceInit] 1 b (11) 1
< 41003.9788> [InfoBarGenerics] KEY: 11 0
< 41003.9798> Traceback (most recent call last):
< 41003.9798>   File "/usr/lib/enigma2/python/Components/ActionMap.py", line 72, in action
< 41003.9803>   File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1013, in keyNumberGlobal
< 41003.9805>   File "/usr/lib/enigma2/python/Components/Timeshift.py", line 492, in checkTimeshiftRunning
< 41003.9806>   File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1038, in recallPrevService
< 41003.9808> AttributeError: 'InfoBar' object has no attribute 'service_types'
< 41003.9809> [ePyObject] (CallObject(<bound method NumberActionMap.action of <Components.ActionMap.NumberActionMap instance at 0x9dd96e68>>,('NumberActions', '0')) failed)

 

[abu baniaz]

Does it crash if you disable time shifting?

 

[ccs]

I can't make it crash, with or without timeshift, with or without panic button, with or without epg mods phase 2.

EDIT: Haven't tried "Channel selection, make number of digits configurable (#526)"

 

[twol]

Must admit I cannot tie up the crash with the 5.3.034 code

 

[BrianTheTechieSnail]

Isn't a zero special - either the "panic button" (instant go to first channel) or instant return to previous channel in OpenVIX?

 

[HeadBanger]

It makes no difference if I switch time shift off and it still crashes when pressing zero, zero, number (not always first time).

HB

 

[BrianTheTechieSnail]

@HeadBanger:

What if you just press zero yourself?
Does that crash it?

 

[HeadBanger]

Yes, pressing zero, zero nearly always causes VIX to crash.

Am I the only one experiencing this - no one else can replicate it?

HB