<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;color:#00000;'><div><br></div><div><br></div><div class="zmail_extra"><div id="Zm-_Id_-Sgn1"><div><br></div><div>---- On Tue, 29 Jan 2019 01:12:09 +0000 <b>James Abernathy <jfabernathy@gmail.com></b> wrote ----<br></div></div><div><br></div><blockquote style="border-left: 1px solid #cccccc; padding-left: 6px; margin:0 0 0 5px"><div><div>Since I now have my production system on V30 I thought I'd test the v30 <br></div><div>mythfrontend on my RP3 B+.<br></div><div><br></div><div>I used the standard Wiki instructions for mythtv-light on the RP3. I <br></div><div>know it's subjective, but I think the playback of OTA MPEG2 recordings <br></div><div>is a little smoother than it was on v29.1 It's still not as smooth as <br></div><div>the Shield TV version of v30 Mythtv-frontend, but it's close. When I'm <br></div><div>not in test engineer mode, I could watch it with no issues.<br></div><div><br></div><div>However, I did manage to do something that I've not done is years, I <br></div><div>locked up the backend using the frontend. I clicked on Watch TV and <br></div><div>the frontend never started playing any video. After a couple of minutes <br></div><div>I Ctrl-Alt-F1 and logged in to reboot. But before I messed with the RP3 <br></div><div>again I went to the Shield TV and it could not connect with the backend <br></div><div>either. So I ssh'ed into the backend and looked at the log. Nothing <br></div><div>unusual after the video started and nothing until I ran "systemctl <br></div><div>restart mythtv-backend".<br></div><div><br></div><div>Everything recovered nicely, but no record of why the backend locked <br></div><div>up. When I use the systemctl restart it took about 5 minutes before it <br></div><div>completed. I don't know for sure because I had to leave the room. Not <br></div><div>sure of the version that locked up, but I had updated all mythtv <br></div><div>software yesterday. While I had the backend down, I updated again today <br></div><div>with a new verision. <br></div><div>(30.0+fixes-autobuild.201901261750.f11c5ab~ubuntu18.04.1). The RP3 <br></div><div>version is mythtv-light/stretch,now 30.0-3-g44fee4bc8a-0 armhf<br></div><div><br></div><div>Jim A<br></div></div></blockquote></div><div><br></div><div>i too upgraded my system to 30 today. while i do have rpi3 FE's, it wasnt the reason mine crashed.<br></div><div>git'd both the BE and primary FE this morning since centos repo's haven't got 30 yet. All seemed to be working fine when I tested in the afternoon but then the other half got her fingers on the remote about 8pm and saw a segfault in mythBE after she clicked into liveTV & then guide. nothing that looks useful to bug yet, but i'll keep an eye on it&git commits. See if i can get time tomorrow to figure out which verbose options i need to start the BE with for more info.<br></div></div><br></body></html>