[mythtv-users] 0.26 recording rules - "not listed"

[Adrian Saul]

Adrian, I've also been seeing this since performing
> 1) the Mysql timezone load, and
> 2) removing my daily mythbackend reboot as no longer necessary (wrong!).
>
> Reinstating the daily mythbackend process restart is a workaround and 
> temporarily removes the problem, for about 24h.
> I had thought it may have been shepherd (and given your GMT+10 I'm 
> guessing you also might be in Australia)
> but disabling program guide updates had no effect, I've only seen 
> complaints on the mailing list from GMT+10 which is why I was looking 
> at shepherd.
> Setting every don't do EIT flag I could find (overall, tuner, channel) 
> has also had no effect.
>
> Something else is confusing mythbackends time sense.
>
> In the past this sort of problem is usually solved by someone else the 
> moment I start digging into the code. I might have to try invoking 
> that method again and see if it works.
>

I have been using the IceTV service, not shepherd so it rules that out.  
I also have EIT disabled on the tuners.

Having burned many late nights over the last week on upgrading to 0.26 I 
am not keen to spend dive into debugging this via code reading, but I 
fear thats the only way as I can't see anything obvious in what appears 
in the database or logs.    The most annoying part is that you can only 
catch this if you see something disappear.