[ATrpms-users] mythtv 0.25 segmentation faults with mythpreviewgen and mythmetadatalookup
jerome at hettich.org.uk
Mon Apr 16 22:18:25 CEST 2012
Update - some progress made -
following a reboot it actually appears that neither mythbackend and
mythfrontend would run either (immediate seg fault for these too)
however removing and reinstalling 0.25-285 rpms seems to have
(temporarily?) resolved this. ie:
yum remove mythtv*
yum remove libmythtv*
yum install mythtv
and everything now seems to be working...
no idea why this would be - so any suggestions as to what was going on
would be very helpful so I can prevent this happening again. Why would
removing an reinstalling the same rpm cure the seg faults - this isn't
On 15 April 2012 22:51, Jerome Hettich <jerome at hettich.org.uk> wrote:
> Hi all,
> have just upgraded a F16 mythtv 0.24 system (combined backend/frontend) to
> 0.24 via installing the 25-284 and then 0.25-285 rpms - thanks for
> providing these Axel!
> most things (recording and frontend) seem to be working fine but the
> backend log contains a number of:
> 2012-04-15 22:22:19.546395 E [1764/27581] HttpServer200
> previewgenerator.cpp:254 (Run) - Preview: Encountered problems running
> '/usr/bin/mythpreviewgen --size 0x0 --chanid 2007 --starttime
> 20120415214700 --outfile "/media/recordings/2007_20120415214700.mpg.png"
> --verbose general --logpath /var/log/mythtv --loglevel info --quiet' (140)
> and running mythpreviewgen (and mythmetadatalookup) with any paramaters
> just seems to result in seg fault:
> [mythtv at Beaker ~]$ mythpreviewgen
> Segmentation fault
> [mythtv at Beaker ~]$ mythmetadatalookup
> Segmentation fault
> Can anyone suggest any steps to help diagnose this issue (or is this a
> question for the mythtv users list)?
> Additional info:
> a few days prior to upgrading to 0.25 I fully working 0.24 (0.24-280) to
> 0.24.2-281 and after this update all mythprograms just seg faulted
> (mythbackend, mythfrontend and mythtv-setup). It is very possible yum would
> have updated other things at the same time but yum.log does not stretch
> back this far - so I have not been able to establish what this would have
> any help greatly appreciated!
> [mythtv at Beaker ~]$ rpm -qa|grep myth
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the atrpms-users