[mythtv-commits] Ticket #12612: New installs die after a few days fixes/0.27 (v0.27 (v0.27.5-71-ga62fc0d)

MythTV noreply at mythtv.org
Sat Feb 20 09:48:01 UTC 2016


#12612: New installs die after a few days fixes/0.27 (v0.27 (v0.27.5-71-ga62fc0d)
----------------------------------+--------------------------------
 Reporter:  singogli@…            |          Owner:
     Type:  Bug Report - General  |         Status:  infoneeded_new
 Priority:  minor                 |      Milestone:  unknown
Component:  MythTV - General      |        Version:  0.27.5
 Severity:  medium                |     Resolution:
 Keywords:                        |  Ticket locked:  0
----------------------------------+--------------------------------

Comment (by dekarl):

 Replying to [comment:10 singogli@…]:
 > The only way to discover them I could find was to backup the entire
 database with mysqldump and then search the entire database with gedit for
 the offending \0 byte. Once the problem is identified this way than the
 mysql replace commands do the fixes.
 ...
 > The channel that caused this is an Albuquerque OTA channel 21.3.

 Lets see if we can get closer to the root cause.

 Was that a NULL character at the end of the string? What was the complete
 string?

 "Albuquerque OTA channel 21.3" sounds like US ATSC?

 Is that an import of channels from Schedules Direct, an OTA channel scan
 with mythtv-setup or some XMLTV import?

 I'm wondering if we have to strip trailing NULL characters from strings
 that come over the air in our string decoding functions.

--
Ticket URL: <https://code.mythtv.org/trac/ticket/12612#comment:12>
MythTV <http://www.mythtv.org>
MythTV Media Center


More information about the mythtv-commits mailing list