51 replies to this topic

[jeanclaude]

I thought this issue was fixed ?

updated an hour ago, and after restart got the popup "timers.xml is corrupt".

indeed - when checking /etc/enigma2 I don't seem to have a timers.xml any more .......... I do have a timers.xml_old but how do I put this one back ?

just renaming doesn't seem to work. And if I restart enigma2 I end up with an empty timers.xml - aha - got it : enigma2 is writing the empty file while closing down............

would it work if I abort enigma2 with "init 4", rename the backup & relaunch with "init 3" ?

[Rob van der Does]

It should. The timers are held in RAM, so you can only change the file manually when E2 has been stopped.

[jeanclaude]

busy trying it .................. OK, it's working indeed !

but what's going on with openPli xml processing ? first autotimer goes dead, and now the timers themselves ........... not very reassuring.......

[WanWizard]

The problem isn't in OpenPLi, the problem is in the EPG data, which contains illegal characters. The fixes are attempts to filter these out, but they are workarounds at best.

[ims]

could you attache timers_old.xml here ? Or tell service name and orbital position and event.

 

Problem was fixed and there is no problem more.

 

May be, you created timer with problematic char (control code) but you did not need restart e2 => error was not discovered. Today you updated e2 and after restart e2 tried open this .xml.

Edited by ims, 19 September 2016 - 17:31.

[jeanclaude]

yes, I did make a backup of this timers.xml_old (renamed back to .xml for uploading) before making any manipulations :

 timers.xml   38.62KB   5 downloads

 

strangely enough this "old" timers.xml file was accepted by enigma2 after my "init 3" command.

[ims]

if you need it, here is repaired this file ... Problem was on "Voyager: To the Final Frontier"

Attached Files

•  timers.xml   38.62KB   5 downloads

[WanWizard]

Hmm, there is that ^U again. This happens a bit to often for my liking, where does it come from?

[ims]

I think, timer was created, when was 2 days in e2 bug ... and was not restart gui or restart box, bug was not activated.

[jeanclaude]

my dm8000 is normally relaunched on Mondays when I do a software upgrade so it's quite possible that the timer had been set a few days before.

I still find it strange that I got no error ofter reinstalling the timers.xml & executing an init 3.

but then again, I didn't check all the timers - now that I know it's the "voyager" timer I'll have a look tonight if the timer is still available in the timerlist or if it has somehow been filtered out.

this timer has been set from the epg list, that I know for sure - probably one of the uk channels - can't recall by heart

and all epg is coming in from the xmltv plugin - nothing else.

Edited by jeanclaude, 20 September 2016 - 15:38.

[WanWizard]

I've looked for it, but it's an recording for Sept.18th, two days ago. Very likely that is was added to the timer list last week.

[jeanclaude]

I see it was a recording on BBC FOUR on September 19th at 01:20 something .........

so I updated later that day, after the recording was made. And after recovery I can't find the timer any more in my timers list, it seems to have been removed.

OK, if this happens again I'll know what to do about it.

thanks guys........