[mythtv-users] backend crashed, recording rules ignored, odd frontend
Jerome Yuzyk
jerome at supernet.ab.ca
Wed Oct 14 22:23:59 UTC 2015
[0.27.4 on Fedora 22]
I just had my first-ever mythbackend crash, logging this:
2015-10-14 15:24:11.135097 C [30553/30553] CoreContext signalhandling.cpp:305 (handleSignal) - Received Segmentation fault: Code 1, PID 927826064, UID 32575, Value 0x00000030
I was recording a baseball game over firewire on my new DCX-3200M P3. Had a couple 0-byte recordings last night from it, but recordings made from it this morning, before the crash, look fine.
Perhaps the crash is part of dealing with my new setup, but I found 2 odd things:
1 - I had to re-create a couple recording rules because they just didn't work. I made trvial changes and re-saved them but got no results in Upcoming Recordings on Mythweb, which is usually rock-solid. They were rules I tweaked yesterday to prefer the new tuner, and last night's shows were recorded, though on my PVR-500 because something else won out. Then this afternoon after the crash (when I noticed) there's no way to make those old rules work. There are no conflicts shown to indicate they're pushed aside, nor is there anything that would. They just stopped working.
2 - Maybe it's circumstantial and I just noticed it, but using the MythCenter-Wide theme on my frontend, the light-green highlighting in the 2nd column of Watch Recordings extends to (and presumably beyond) the right side of the screen. Not lining up with curved corners like when an item in that column is highlighted. There's a snapture at http://www.imageno.com/ss7ab5asb51npic.html, look at how the highlighting bleeds to the right on the 2nd line.
--
A little of Jerome's MythTV World: http://mythtv.bss.ab.ca
More information about the mythtv-users
mailing list