[mythtv-users] Replace my database with a "stock" one

[Rob Owens]

After an upgrade to 0.26, then quickly to 0.27, my backend system is experiencing a lot of problems that I've never seen in my many years of running MythTV.  Commercial flagging isn't working.  Mythfilldatabase no longer runs automatically (but it works when I run it manually).  I cannot watch a recording until it is done recording (although watching live TV works).  When skipping forward, I often get the “End of Recording” menu which asks to Delete or Save.  If I save, I can watch the recording in its entirety.  There are probably other issues, but I've been dealing with them for so long now that they're starting to seem normal to me.

Rather than trying to fix these problems one-by-one, I was wondering if it makes sense to replace my database with a “stock” one, then restore the tables for things that I would like to preserve (recordings, previously-recorded, recording schedule, etc).  Any opinions on whether that is a good idea or not?  My thought was to get all the settings back to their defaults and see if things work right.

Background:

My problems started about 7 months ago when I upgraded my Debian Squeeze system to Wheezy, and moved from mythtv 0.25 to 0.26 (from www.deb-multimedia.org).  There was a bug which made my backend crash whenever I tried to record with a PVR-150.  So I upgraded again to 0.27 (www.deb-multimedia.org's Wheezy backports) and got my basic functionality back, but have experienced a lot of nuisance problems ever since.

This is a 32-bit system, in case that matters.

Thanks for any advice you can give.

-Rob