<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">While I am all for helping out others, this is an Apples to Oranges</div>
</div>
comparison. You are comparing an upgrade to a fresh install, which are<br>
very different things and can each cause their own issues. I have<br>
always recommended doing a backup/fresh install/restore over a<br>
distribution upgrade.<br>
<br>
In your response, you are implying that the issue you had was a direct<br>
result of 64-bit being buggy. This is simply not the case, there are<br>
many users who have run the 64-bit version for years without issue.<br>
You went straight for the 32-bit install when you were having issues<br>
with an upgraded system without even trying a freshly installed 64-bit<br>
system. That seems like bad logic/troubleshooting.<br>
<br>
My money is on a broken upgrade, not the 64-bit OS.<br>
<br>
Thanks,<br>
<br>
Thomas Mashos</blockquote><div> </div></div><div>Thanks for the assumptions... After backing up my database I fresh installed Mythbuntu 64-bit, and ran into issues. First one is that the 64-bit database upgrade left me two schema revisions behind. I tried reinstalling 64-bit a number of times with the same results, and same error 139 CTD issues every time. Could it be my hardware? Sure... two completely different 64-bit systems. I would love to be running 64-bit Mythbuntu, but for some reason it just doesn't like me.</div>
<div><br></div><div>My first post was the abridge version. OP doesn't have to listen to me, I was just offering troubleshooting advice and clearly stated it might or might not work for him.</div>