<br><br><div class="gmail_quote">On 12 December 2012 03:57, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1307 is the 0.26 DB schema version.<br>
<br>
1299 is the DB schema version for 0.25.<br>
<br>
So, you have 2 different MythTV versions installed (likely one in /usr/local and one in /usr) and, because of differences in PATHs, your service start script runs 0.25 (likely in /usr) and your user runs 0.26 (likely in /usr/local).<br>
<br></blockquote><div><br>surely thats a bug isn't it, Mike? (not that i could bug fix this)<br>Doesn't make much sense in my mind to have both versions installed.<br><br>anyway, my VM machine has this issue (on 0.25, BE on 0.26-fixes), this is what i did to fix it:<br>
- mythbuntu-control-center > repos > refresh (so you should now see 0.25, 0.26 and 0.27 in the dropdown box). Select 0.26 and apply it.<br>- apt-get update<br>- apt-get upgrade - take note here; libmyth-0.25-0 will be upgraded (this is incorrect)<br>
once updated, you'd expect mythfrontend to run ok. no, it won't.<br>- apt-get autoremove libmyth-0.25.0<br>you'll see that libmyth-0.26.0, and a few mythtv-* packages will now be updated/installed.<br>- start mythfrontend and all should work fine now.<br>
<br><br></div></div>