Thanks cesman, you rock!
Not quite sure what to look for, but here are some things I found in the logs:
In mythbackend.log
QSettings: error creating /.qt
QSettings: filename is null /empty
(I searched on this one and it seems it isn't usually a problem, but I have about eight or ten of these very often in the log.)
KICK DATABASE
SELECT NULL; // hmm. Why select null?
(seems weird, but was only in the log once, not when the programs were turning themselves off.)
MPEG2VIDEO @ 0x8111d8] ac-tex
MPEG2VIDEO @ 0x8111d8] damaged at 12 7
MPEG2VIDEO @ 0x8111d8] concealing errors
MPEG2VIDEO @ 0x8111d8] MVs not available
(I don't know if any of these are a problem and was only in the log once--not too near the time my program ended itself in the middle.)
In debug log file:
mythtv kernel: ivtv iflags=8, 3 s_sflags=4
mythtv kernel: ivtv iflags=a, 3 s_sflags=4
(there were a number of these types of messages)
In messages log file:
mythtv kernel: DMAP not set
(a number of times)
I ran a repair of some of the corrupted MySQL database tables as mentioned in another thread. There seemed to be about 4 or 5 corrupted tables (record, recorded, recordedmarkup, oldrecorded, cardinput).
I don't know enough to know if any of these messages look ominous. I mostly saw other things that looked normal in the logs (such as playback started, recording started, etc.).
The weird part about some of it was that it looked like some of the programs that were cut off half way through showed that they supposedly stopped recording at the correct times in the log.
Thanks again. I would've never got this working without all the good help here. I wish I weren't such a Linux newbie so I could be more helpful to others instead of always needing help. Maybe when the semester ends and I have more free time I can write up some info about how I got everything working to help other newbies like me out.
|
I'm thinking MythTV is pretty useful and cool at this point since I can rely on it to be stable now.