[mythtv-commits] Ticket #2084: Channel table seems to get corrupted either over time or after scan

[MythTV]

#2084: Channel table seems to get corrupted either over time or after scan
-----------------------------------+----------------------------------------
 Reporter:  tim at wheresrover.co.uk  |        Owner:  danielk
     Type:  defect                 |       Status:  closed 
 Priority:  minor                  |    Milestone:  0.20   
Component:  mythtv                 |      Version:  head   
 Severity:  medium                 |   Resolution:  invalid
-----------------------------------+----------------------------------------
Comment (by tharding at cs.utah.edu):

 Daniel,

 I have the same problem. I have been digging into this issue and I am
 seeing some stuff in the logs that look problematic. In my log I see a
 query that looks wrong.

 The query at line 836 returns nothing when I run it in mysql, but if I
 change the end to defaultinput = 'Television', instead of inputname =
 'Television' it works. For the DVB card, the inputname is set to
 'DVBInput'. I couln't tell from the log why it selected 'Television' for
 the search. My guess is that the capturecard.defaultinput database is
 getting set wrong to 'Television' instead of 'DVBInput'. This looks like
 it causes the default channel to be set to '5.0' the first channel listed
 in the database for this card.

 At this point it looks like fails to tune for some reason (I can tune to
 this channel outside of mythtv), and moves into the same loop as described
 above. The loop appears to only happen for live TV, for recordings it just
 doesn't record anything, but seems to recover fine.

 I am including my log, and table dump.

 Tyson

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/2084#comment:5>
MythTV <http://www.mythtv.org/>
MythTV