[mythtv-users] Commercial Flagging (UK, DVB-T)

Andrew Leech coronasensei at gmail.com
Sun Nov 4 23:49:01 UTC 2012

On 28/10/12 3:37 PM, Andrew Leech wrote:
> On 28/10/12 8:09 AM, Tim Phipps wrote:
>> Quoting Andrew Leech <coronasensei at gmail.com>:
>>> On 27/10/12 9:24 PM, Mark Greenwood wrote:
>>>> On 27 Oct 2012, at 07:56, Andrew Leech wrote:
>>>>>  File "./mausc-wrapper", line 18, in runjob
>>>>>    db = MythDB()
>>>>> <deleted>
>>>>> as my libmyth-python 
>>>>> (2:0.25.2+fixes.20121002.139bd59-0ubuntu0mythbuntu1)
>>>> I'm using mythbuntu 12.04.1, which has python 2.7.3. I'm no python
>> I don't think that will help. I'm on crufty old Debian stable and it 
>> has python version 2.6.6. The MythDB() call is where the failure is 
>> rooted. Can you run mythpython and type 'db=MythDB()' into it?
>> Cheers,
>> Tim.
> Hi Tim,
> Yeah you're right, it's quite a reproducible failure. I had to type:
> >>> from MythTV import MythDB
> before  db=MythDB() would resolve but that does trigger the same failure.
> Looks to me like something is out of whack with my mythtv 
> library/bindings, probably updating mythtv and ensuring all the 
> packages are up to date would help before updating the entire system.
> I'm always a little reticent about doing updates to mythtv, I want to 
> be sure I have a bit of spare time in case I have new problems to fix. 
> I might have to wait a bit, it's far too nice a day outside today to 
> dive into a myth update just now! I'll try that later.
> Thanks,
> Andrew
Follow up, it had nothing to do with python problems, it turns out it's 
because I had an empty ~/.mythtv/config.xml . I did have an 
/etc/mythtv/config.xml but apparently that's no use.
So score one for nasty cryptic error messages!

I'll follow up later with some commercial flagging results.

More information about the mythtv-users mailing list