[mythtv-users] mythbackend crashes on any recording in Fedora 28

[John Pilkington]

On 07/06/18 10:38, Jake wrote:
> On 05/06/18 23:45, Greg Woods wrote:
>>
>>
>> On Tue, Jun 5, 2018 at 1:17 AM Jake <mythmail at runbox.com 
>> <mailto:mythmail at runbox.com>> wrote:
>>
>>
>>
>>
>>
>>
>>     ) I was going to ask why they were rated as "medium" severity and
>>     "minor" priority in the mythtv trac.  People affected by this bug
>>     cannot use MythTV on any frontends any time a recording is active.
>>
>>
>> Yes, but only a small minority of MythTV users are on Fedora 28.  I am 
>> glad for this list and for your efforts at testing, because I am also 
>> a Fedora user and I was able to stop at F27 for now and avoid this. I 
>> had enough trouble with the 0.28 to 0.29 Myth upgrade.
>>
>> --Greg
>>
>>
> 
> Thanks Greg.
> 
> I wish anticipated this as my family has now used up our ISP's data 
> quota for the month using Netflix and I've had to buy additional data 
> blocks!
> 
> I used to keep a test VM in step with my main backend to do basic 
> testing before upgrading, but haven't had time to try it.  I built it 
> all years ago, before we had children...
> 
> On that note, I personally don't have much time for watching TV. 
> Troubleshooting this has used a lot of my free time.  So I hope other 
> people will excuse me if I don't volunteer to help more (assuming that I 
> actually have the knowledge to do so).  I offered to test, as that's all 
> I can do now.
> 
> 
> 
> Hi Richard,
> 
> I'm sorry to bug you, but could you please check that you were able to 
> submit builds of the 20180529 update for Fedora 28 or 27?
> I can only see the (successful) build you ran for Fedora 29 on the 1st 
> of June (http://koji.rpmfusion.org/koji/buildinfo?buildID=7595).
> 
> 
> If there was an alternate work-around, short of reinstalling Fedora or 
> trying to compile this myself, I'd be trying it now.
> 
> Thanks again,
> Jake

Publishing does seem to be taking rather a long time.  This link 
probably isn't intended for widespread use but might help:

http://koji.rpmfusion.org/koji/packageinfo?packageID=162

General 'pushes' to the repo were reported on  17, 21, 29 May and 1, 4 
June.  I do expect it will be soon now, but who knows?