Author: Frank Hartmann Date: To: dmo-discussion Subject: Re: No EPG data for ProSieben since last Mythtv update
Christian Marillat <marillat@???> writes:
> Stephan Seitz <stse+debian@???> writes:
>
>> On Wed, Apr 03, 2013 at 02:12:24PM +0200, Christian Marillat wrote:
>>>Stephan Seitz <stse+debian@???> writes:
>>>> My last MythTV update is from 2013-03-12 (mythtv:amd64
>>>> 0.26.0+fixes20130228-dmo1 -> 0.26.0+fixes20130311-dmo1).
>>>New mythtv packages are stuck in unstable as I don't know if this bug
>>>has been fixed or not.
>>
>> To be honest, I am completely confused with this bug.
>> I’m using now 0.26.0+fixes20130330-dmo1.
>>
>> Sometimes I got an EPG update, sometimes not. First I thought I will
>> get an update after restart, but this is not the case. If I let mythtv
>> run for more than a day, I don’t get an update either. But sometimes
>> it happens.
>> But I only notice a problem with Prosieben (EPG data are now expired,
>> 2013/04/04 2:30 AM CEST), and it seems, I am the only one.
>>
>> I will try to get help from the mythtv list (probably at the weekend).
>
> Do you have found a solution for this problem ?
Hi,
I am using since a few days mythtv-backend 0.26.0+fixes20130330-dmo1 and
have received EPG updates for ProSieben. I am using DVB-S2 too.
Isn't there a correlation between the channels you record and the
channels for which EPG is captured? If you never record from the group
of channels where ProSieben is in, you will not have any EPG for
ProSieben either?