<br><br><div class="gmail_quote">On Wed, May 16, 2012 at 5:35 PM, Raymond Wagner <span dir="ltr"><<a href="mailto:raymond@wagnerrp.com" target="_blank">raymond@wagnerrp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 5/16/2012 16:59, Aaron wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
First one is that the 64-bit database upgrade left me two schema<br>
revisions behind.<br>
</blockquote>
<br></div>
MythTV 0.25 was released on April 10th to schema revision 1299, and the developmental branch was updated to revision 1301 on April 13th. That's two schema revisions. Any chance what you were seeing was accidentally installing the developmental branch rather than 0.25-fixes?<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I tried reinstalling 64-bit a number of times with the same results,<br>
and same error 139 CTD issues every time. Could it be my hardware?<br>
Sure... two completely different 64-bit systems.<br>
</blockquote>
<br></div>
Exit code 139 means... invalid time zones. You configured different time zones for your frontend and backend, causing the frontend to immediately terminate with that error. The logs of either the frontend or backend would confirm.<br>
<br>
<a href="http://code.mythtv.org/cgit/mythtv/tree/mythtv/libs/libmythbase/exitcodes.h#n22" target="_blank">http://code.mythtv.org/cgit/<u></u>mythtv/tree/mythtv/libs/<u></u>libmythbase/exitcodes.h#n22</a><br>
<br>
In past versions, error 139 would be an aliased segmentation fault, or signal 11 (+128), however I do not believe 0.24 or 0.25 behave in that manner.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My first post was the abridge version. OP doesn't have to listen to me,<br>
I was just offering troubleshooting advice and clearly stated it might<br>
or might not work for him.<br>
</blockquote>
<br></div>
The troubling issue is that the AMD64 architecture was released over nine years ago. AMD and Intel both stopped shipping desktop hardware not capable of 64-bit operation by 2006. AMD64 has been the primary architecture for use on Linux for years, and yet with over 2/3 of the entries on Smolt running Ubuntu 12.04, over half the users are still running 32-bit, and there are still blind recommendations to others to run 32-bit.<br>
<br>
Running 32-bit Linux should be a last resort for either a known problem with a particular piece of hardware, or when all other attempts at resolving an error has been exhausted.<div class="HOEnZb"><div class="h5"><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>
</div></div></blockquote></div><br><div>Thanks for the tips Raymond, it would have been nice to know that info 9 days ago when I posted "<span style>Mythfronte</span><span style>nd crashing 0.25 on Mythbuntu 12.04".</span></div>
<div><span style><br></span></div><div><span style>Damien, I'm sorry, I was just trying to help ya out... I'll shut up and bow out....</span></div>