Has this been fixed or is there any activity on this problem? I just upgraded to 16.10 today and after running into the usual mysql password problem, I gave up and purged mysql and mythtv, deleted all mythtv files and directories, rebooted, and reinstalled mythtv from scratch.
I have the same continuously restarting frontend with exit code 139.
As an aside, I have been running mythtv on ubuntu for over 5 years and an ubuntu upgrade rarely manages to complete without killing mythtv. It doesn't break every time but most times it does which usually burns a whole day since I can't remember if this fix will be the same as last version fix or the same as last year's fix. I'm not a linux pro so I have to relearn all those terminal commands I haven't touched in 6 months. Plus little things like mysql commands on the mythtv troubleshooting page that no longer work unless you add the -p parameter which current versions of mysql now require and mysql does not say -p is missing, it just fails leaving you wondering why.
Has this been fixed or is there any activity on this problem? I just upgraded to 16.10 today and after running into the usual mysql password problem, I gave up and purged mysql and mythtv, deleted all mythtv files and directories, rebooted, and reinstalled mythtv from scratch.
I have the same continuously restarting frontend with exit code 139.
As an aside, I have been running mythtv on ubuntu for over 5 years and an ubuntu upgrade rarely manages to complete without killing mythtv. It doesn't break every time but most times it does which usually burns a whole day since I can't remember if this fix will be the same as last version fix or the same as last year's fix. I'm not a linux pro so I have to relearn all those terminal commands I haven't touched in 6 months. Plus little things like mysql commands on the mythtv troubleshooting page that no longer work unless you add the -p parameter which current versions of mysql now require and mysql does not say -p is missing, it just fails leaving you wondering why.