Vu+ Ultimo 4K with 3TB HDD, Dual FBC (Sat) tuners, 1x Twin Hybrid DVB-C/T/T2 tuner
Vu+ Solo 4K with 1TB HDD, Dual FBC (Sat) tuners, 1x Hybrid DVB-C/T/T2 tuner
Vu+ Solo 2 with 1TB HDD 'White Edition', 2x DVB-S2 tuners
Mut@nt HD2400 with 1TB HDD, 4x DVB-S2 tuners
Fixed 28.2E Technomate 65cm Mesh Satellite Dish with Inverto Unicable II/JESS LNB and Inverto Unicable Splitter
Fixed 28.2E Sky Zone 1 45cm Satellite Dish with Octo LNB
(All receivers installed with the latest Dev build)
Yes I realise OP said satellite but strange crash log is exactly the same! By the way it was type 4097 not type 1 iptv.
Last edited by spanner123; 23-05-20 at 17:01.
Are you using a plugin that replaces the InfoBarGenerics.py file?
abu baniaz (24-05-20)
Maybe a clue just tried an instant record again and it's ok. Difference is this channel has an epg the other one didn't!
twol (23-05-20)
Gigablue Quad 4K & UE 4K
.........FBC Tuners:
------------------> GT-Sat unicable LNB to 1.5M dish(28.2E)
------------------> Gigablue unicable LNB to 80 cm dish(19.2E)
.......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
Zgemma H9 C/S into Giga4K
When it crashed twice first was stop after current event although no epg so I tried it with record indefinately and it still crashed. In the past wth no epg even you you selected stop after current event it would bring up a message saying recording indefinately if there was no epg.
If you disable the split timer function, do you get the same crash?
abu baniaz (23-05-20)
removed jedimaker just in case and tried again still get crash. Latest log:
<108551.9101> 19:24:52.8186 [eInputDeviceInit] 0 a7 (167) 1
<108551.9121> 19:24:52.8205 [InfoBarGenerics] KEY: 167 RECORD
<108552.7732> 19:24:53.6816 [eDVBFrontend1] close frontend
<108552.7746> 19:24:53.6831 [eDVBFrontend1] setVoltage FE_ENABLE_HIGH_LNB_VOLTAGE 0 FE_SET_VOLTAGE 2
<108552.7869> 19:24:53.6953 [eInputDeviceInit] 1 6c (108) 1
<108552.7891> 19:24:53.6975 [InfoBarGenerics] KEY: 108 DOWN
<108552.7907> 19:24:53.6991 [ActionMap] Keymap 'WizardActions' -> Action = 'down'.
<108553.0171> 19:24:53.9255 [eInputDeviceInit] 0 6c (108) 1
<108553.0193> 19:24:53.9277 [InfoBarGenerics] KEY: 108 DOWN
<108553.3017> 19:24:54.2102 [eInputDeviceInit] 1 160 (352) 1
<108553.3040> 19:24:54.2124 [InfoBarGenerics] KEY: 352 OK
<108553.3058> 19:24:54.2142 [ActionMap] Keymap 'WizardActions' -> Action = 'ok'.
<108553.3846> 19:24:54.2930 Traceback (most recent call last):
<108553.3873> 19:24:54.2957 File "/usr/lib/enigma2/python/mytest.py", line 244, in processDelay
<108553.3964> 19:24:54.3048 callback(*retval)
<108553.3983> 19:24:54.3067 File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 3131, in recordQuestionCallback
<108553.4003> 19:24:54.3087 File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 3043, in startInstantRecording
<108553.4024> 19:24:54.3108 File "/usr/lib/enigma2/python/RecordTimer.py", line 191, in __init__
<108553.4045> 19:24:54.3129 AttributeError: 'iPlayableServicePtr' object has no attribute 'isRecordable'
<108553.4063> 19:24:54.3147 [ePyObject] (CallObject(<bound method Session.processDelay of <__main__.Session instance at 0x634eac38>>,()) failed)
Just noticed this when comparing boxes......
Is this .py file meant to be there?Code:root@et10000:~# ls -l /usr/lib/enigma2/python/mytest.py* -rw-r--r-- 1 root root 21709 May 21 14:02 /usr/lib/enigma2/python/mytest.py -rw-r--r-- 1 root root 22942 May 21 14:02 /usr/lib/enigma2/python/mytest.pyo root@et10000:~#
ccs (23-05-20)
Tried recording (indefinitely) with a 4097 service ref and no issues at all - with and without new time split feature.
PS: I also have two mytest.* files