<br><br><div class="gmail_quote">On Wed, May 16, 2012 at 2:34 PM, Damian <span dir="ltr"><<a href="mailto:myth@surr.co.uk" target="_blank">myth@surr.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello all,<br>
<br>
My last thread got confused by my power supply dying as I was trying to sort things out. That's been replaced now so I'm back to the problems caused by the upgrade.<br>
<br>
'Bill' gave me some help off of the list yesterday, but we got to a point that he didn't know how to get past. Following his advice, this command:<br>
<br>
sudo mythbackend -v most --user mythtv --nodblog<br>
<br>
Returns this:<br>
<br>
mythbackend: symbol lookup error: /usr/lib/x86_64-linux-gnu/<u></u>libva-x11.so.1: undefined symbol: fool_postp<br>
<br>
Any ideas where to go from there?<br>
<br>
Background information:<br>
I had Ubuntu 11.10 (with gnome) running MythTV 0.24 by having the MythBuntu packages installed. There are problems now and the (usually around updates), but everything has been fine for a few months.<br>
<br>
I wanted to see the latest stable version of MythTV, so switched to the 0.25 repository in the MythBuntu configuration area. I then ran the update manager.<br>
<br>
It suggested that I should do a 'Partial' distribution update and I said OK. Everything seemed to go fine except for this:<br>
<br>
<a href="http://pastebin.com/NBztMBdW" target="_blank">http://pastebin.com/NBztMBdW</a> (mythtv.cnf)<br>
<br>
(I don't remember now whether I said to keep the old file or take the new one)<br>
<br>
However, after this had all finished, myth was broken. Frontend just going into a loop of failing and restarting, then realised that the backed wasn't even running!<br>
<br>
Following advice on here, I then ran a full distribution update to take me to Ubuntu 12.04. That process came up with these issues:<br>
<br>
<a href="http://pastebin.com/6ydZ55xm" target="_blank">http://pastebin.com/6ydZ55xm</a> (my.cnf)<br>
<a href="http://pastebin.com/0rJfGd30" target="_blank">http://pastebin.com/0rJfGd30</a> (crontab)<br>
<a href="http://pastebin.com/C0nvSVfj" target="_blank">http://pastebin.com/C0nvSVfj</a> (release-upgrades)<br>
<a href="http://pastebin.com/Ybg6nNxd" target="_blank">http://pastebin.com/Ybg6nNxd</a> (menu.lst)<br>
<a href="http://pastebin.com/HX2kyjvQ" target="_blank">http://pastebin.com/HX2kyjvQ</a> (usr.sbin.mysqld)<br>
<a href="http://pastebin.com/UA3NQab1" target="_blank">http://pastebin.com/UA3NQab1</a> (php.ini)<br>
<br>
All of which I told to replace the old file with the new file, and I kept the details of the 'diff' files above for reference.<br>
<br>
If it helps to find the source of the problem, my music system is also not working. I run SqueezeBoxServer on this same Ubuntu system (which is the house media system and server) and have a couple of SliMP3 and SqueezeBox units attached to the network. They can not currently connect to the server. I have added the lines from the end of the old /etc/apparmor.d/usr.sbin.<u></u>mysqld file back into the replaced file, but the SqueezeBoxSerever still seems to be broken, just like myth.<br>
<br>
Hopefully the problems are connected. I thought describing both may help you all find the solution.<br>
<br>
Please help!<br>
Thanks to the power supply failure, this machine has been having problems for about 2 weeks now. My wife's patience lasted about a week. Now the kids and cat are packing their bags and lining up at the front door! :-)<br>
<br>
Thanks for your time<span class="HOEnZb"><font color="#888888"><br>
Damian<br>
______________________________<u></u>_________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/<u></u>listinfo/mythtv-users</a><br>
</font></span></blockquote></div><br><div>I'm not sure if this will help, but I had massive problems in both upgrading and stability with 64-bit Mythbuntu. I went back and tried 32-bit and have not had a single issue. I tested 32-bit by throwing in a spare old hdd, installing Mythbuntu 32-bit, reimporting the db and tested it. After a day or so, I wiped my 64-bit install and replaced it with the 32-bit.</div>
<div><br></div><div>Again, not sure if it will help but might be worth a try?</div>