Just did an online update from 5.3.029 to 5.3.030 and..........
It still crashes.
Also the tried and tested "switch off at the mains for 5 minutes" didn't help.
Last edited by ccs; 18-05-20 at 19:19.
On the offchance this is something to do with me, can you try replacing /usr/lib/enigma2/python/RecordTimer.py with this
https://raw.githubusercontent.com/Si...RecordTimer.py
OK will take 5 minutes or so.Originally Posted by simonc
I wish I could say it was, but it still crashes.
Last edited by abu baniaz; 02-10-20 at 22:00.
Is this commit a pure coincidence, or......
Code:https://github.com/OpenPLi/enigma2/commit/e1923b7c0d0304fe76218a13bf2d968fc2960bcd
abu baniaz (19-05-20)
ET10K
Software update from 29 to 30 - no crashes
Couch flash from 29 to 30 with settings and plugin restore from 29 - no crashes (My own manual 29 backup and not one produced as a result upgrade/flash)
Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)
No we don‘t have it on ViX.... but it kind of fits - but why does 019 work?
Last edited by twol; 18-05-20 at 20:24.
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
Correct, Zgemma H7S.
I know, just like mine, mentioned in post #1.
Any Ultimo4k owners (or H7S's) out there now running 5.3.030?
Last edited by ccs; 18-05-20 at 22:15.
I've just software updated a H7C from 5.3.027 to 5.3.030.
That commit was added to fix this crash reported by IMS, which seems to be the same as the one being reported.
Code:Backtrace: /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0xA4DDC] /lib/libc.so.6(__default_rt_sa_restorer) [0xB6C4FC60] /lib/libc.so.6(gsignal) [0xB6C4E94C] /lib/libc.so.6(abort) [0xB6C4FDC4] -------FATAL SIGNAL
Reason was
This issue appears with the new "speedup" from netifaces.
Parsing the output from ip/ifconfig commands didn't show that issue.
Why it appears now? I have no idea, but the flow is now the same as before, now we are starting some services earlier / faster.
If creating an std::string and passing the const c_str to enigma fixes the issue that is enough for me.
Same problem here. Here is my log...
Enigma2_crash_2020-05-19_04-50-51.log
VU+ Duo 4K SE
ccs (19-05-20)
So you reckon this commit may well fix my (and other posters) crashes?
EDIT:
The PLi discussion mentioned this....
so I deleted OWIF and the box no longer crashes.Before we never had the chance to see that error, simply because we where starting OWIF toooooooooo late.
Now OWIF starts tooooooooo fast
Last edited by ccs; 19-05-20 at 10:21.
This is NOT a solution, I was just testing out a theory.
Well the OpenPli change has been added to ViX so next build ..............................This is NOT a solution, I was just testing out a theory.
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
ccs (19-05-20)
Posting Permissions
Reply With Quote