[mythtv-users] Problem Running mythcommflag in 0.23RC
Ian Barton
lists at manor-farm.org
Mon Apr 5 18:47:58 UTC 2010
Michael T. Dean wrote:
> On 04/05/2010 06:27 AM, Ian Barton wrote:
>> I have just upgraded my MBE to 0.23 and am having problems running
>> mythcommflag to clear cut lists. The command I am using is:
>>
>> mythcommflag --clearcutlist -f
>> /media/recordings/mythtv/1020_20100121105900.mpg
>>
>> I am seeing the following errors:
>>
>> mythtv at mythtv:/home/ian$ mythcommflag --clearcutlist -f
>> /media/recordings/mythtv/1020_20100121105900.mpg
>>
> ...
>> 2010-04-05 11:14:32.293 MSqlDatabase::OpenDatabase(), db object is not
>> valid!
>> QSqlQuery::exec: database not open
>> QSqlQuery::exec: database not open
>> 2010-04-05 11:14:32.344 Driver error was [1/-1]:
>> Driver not loaded
>> Database error was:
>> Driver not loaded
>>
>> It looks as though mythcommflag can see the Master backend. I am
>> running the job as the mythtv user and my ~/.mythtv.config.xml looks
>> like:
>
> I'm assuming that's a typo and you really meant ~/.mythtv/config.xml
>
>>
>> <Configuration>
>> <UPnP>
>> <UDN>
>> <MediaRenderer>6248ef12-d606-4866-8d15-81ded57b4c5e</MediaRenderer>
>> </UDN>
>> <MythFrontend>
>> <DefaultBackend>
>> <DBHostName>192.168.0.31</DBHostName>
>> <DBUserName>mythtv</DBUserName>
>> <DBPassword>password</DBPassword>
>> <DBName>mythconverg</DBName>
>> <DBPort>0</DBPort>
>> </DefaultBackend>
>> </MythFrontend>
>> </UPnP>
>> </Configuration>
>
> I'm guessing (based on the directory you're in and the end result) that
> you've sudo'ed or su'ed and you didn't do it properly, so you still have
> the old HOME, so you're not using /home/mythtv/.mythtv/config.xml, but
> using /home/ian/.mythtv/config.xml. To fix it, you should start a login
> shell.
>
I was su'ing to the myth user. However, I have the same config.xml in
/home/ian, which is readable by MythTV. I also get the same errors when
I log in as mythtv. The command is from a script which is run by the
mythtv user. This all worked fine before the upgrade from 0.22->0.23, so
I am assuming it's connected with the upgrade:)
Ian.
More information about the mythtv-users
mailing list