55 replies to this topic

[bobbibob]

Ok, so it crashes as soon as it starts up.

 

This needs to be looked at by a developer I'm afraid.

 

I've added the sanitized bouquet files and enigma config. I haven't tested yet if that last one has any influence.

Thanks so much. I've tried, but it results in the same error.... 

[bobbibob]

Ok, so it crashes as soon as it starts up.

 

This needs to be looked at by a developer I'm afraid.

 

I've added the sanitized bouquet files and enigma config. I haven't tested yet if that last one has any influence.

Hey, I found it..

some plugins (EPGRefresh / EPGSearch and IMDB) that were in the config backup did not run well...

I uninstalled them...

flased including backup and restore,

refreshed the packetlist and installed those and then reinstalled the named plugins...

 

All working fine now, allthough that overall performance of the box is a bit slower... 

 

Thanks for helping out... 

 

Bob

Edited by bobbibob, 4 January 2025 - 15:58.

[WanWizard]

Thanks for the feedback.

 

That sounds like they weren't properly updated when you updated from 9.0 to 9.1. Any change you can post the opkgupdate.log file from /home/root on your box, if that is still holding info about the upgrade?

[ims]

And what about a forgotten .py file in Enigma?
 

[bobbibob]

Thanks for the feedback.

 

That sounds like they weren't properly updated when you updated from 9.0 to 9.1. Any change you can post the opkgupdate.log file from /home/root on your box, if that is still holding info about the upgrade?

I've looked for that file, but since I flashed the box, it is not there anymore (only recent remarks made today) and I can not find it in the backup files from the last couple of days... 

Sorry... 

 

Bob

Edited by bobbibob, 4 January 2025 - 21:53.

[WanWizard]

And what about a forgotten .py file in Enigma?

 Possible, but that can only exist due to manual actions (the source package would update the py's too), and also the installed pyc from the 9.1 build should be newer and override the py.
 
If those plugins were installed from the feed, I expect the opkgupdate.log to show them being updated. If not, we might have a PR server issue.

[WanWizard]

I've looked for that file, but since I flashed the box, it is not there anymore (only recent remarks made today) and I can not find it in the backup files from the last couple of days...

 

Too bad, thanks anyway.

[ims]

 

And what about a forgotten .py file in Enigma?

 Possible, but that can only exist due to manual actions (the source package would update the py's too), and also the installed pyc from the 9.1 build should be newer and override the py.
 
If those plugins were installed from the feed, I expect the opkgupdate.log to show them being updated. If not, we might have a PR server issue.

 

But that's why I wrote 'forgotten file.' Some manual adjustments in a manually uploaded file (which survives updates). And then after the flash, the problem is solved...

[WanWizard]

My point was the pyc in the updated plugin should always have a newer timestamp than any py from before the update, which would cause python to use the pyc and ignore the py.

[bobbibob]

 

I've looked for that file, but since I flashed the box, it is not there anymore (only recent remarks made today) and I can not find it in the backup files from the last couple of days...

 

Too bad, thanks anyway.

 

Hmm, celebrated to early...

In a loop rebooting again...

Attached Files

•  enigma2_crash_1736080553.log   2.12KB   1 downloads
•  opkgupgrade.log   2.41KB   0 downloads

Edited by bobbibob, Yesterday, 13:43.

[ims]

demangled :
 

/usr/bin/enigma2(handleFatalSignal(int, siginfo_t*, void*)) [0x798B0]
/lib/libc.so.6(__default_rt_sa_restorer) [0xB61A40F0]
/usr/bin/enigma2(eDVBService::isPlayable(eServiceReference const&, eServiceReference const&, bool)) [0xA5700]
/usr/bin/enigma2(n/a) [0x1A0AA4]

[WanWizard]

So still the same crash.

[bobbibob]

Yes, and guess what.. Now all of a sudden it runs well... it came out of the loop

I did not do anything... 

 

Can i upload some file to check whats wrong? 

 

Bob

Edited by bobbibob, Yesterday, 14:12.

[WanWizard]

The only thing I can think of is invalid EPG data, as a variable, everything else in the config is static. And when Enigma crashes, it looses the EPG data it has received.

[ims]

After clean flash it works and after restore backup it starts crash or what ?

[bobbibob]

After clean flash it works and after restore backup it starts crash or what ?

Yes it seems so...  But i have not run the clean flash for long ofcourse,,, 

[bobbibob]

The only thing I can think of is invalid EPG data, as a variable, everything else in the config is static. And when Enigma crashes, it looses the EPG data it has received.

So maybe uninstall the EPG plugins and delete the epg.dat files? And reinstall? 

[WanWizard]

If it has started up ok, that means we can assume the current epg.dat cache file is correct.

 

My assumption is that somehow something is received (either via EPG refresh, EPG import, or OTA by zapping to a channel with EPG) which contains some corruption. This is stored in epg.dat when you restart Enigma (or the box), and when it starts again, and reads the epg.dat, it crashes.

 

We can test this hypothesis by waiting for the next crash, when that happens rename (not delete) epg.dat and restart. If the hypothesis is correct, it will start correctly, but without pre-loaded EPG. If this is so, please zip that renamed epg.dat file and post it here.

[Stan]

I've been meaning to ask, what is the EPG option 'Correct invalid EPG data' for?

[WanWizard]

It attempts to repair non UTF-8 data: https://github.com/O.../event.cpp#L213

 

If set to "Debug" it will write every correction to the debug log ( but to see that E2 needs to be started in Debug mode, which requires a change to /usr/bin/enigma2.sh )

 

I don't know at what point that happens, and if it happens for every possible source of EPG data.