me-tv-development team mailing list archive

[Michael Lamothe <michael.lamothe@xxxxxxxxx>]

What version are you using?

2008/5/3 Svartalf <frank@xxxxxxxxxxxxxxx>:
> Apparently, it is back.  And moreover, whatever's generating the problem
>  seems to be boggling the channels.conf file on scanning.  I've gotten a
>  mixed bag of stuff out (apparently, the station ID feed data from the
>  channel isn't coming through clean on my HVR-1250- stations tune in NICE
>  though when the stuff mostly works...) of the process, ranging from an
>  almost empty file to a mostly filled file that there's no editing to be
>  done on the channels.conf that will make it happy.  (Going to comment on
>  THAT bug in it's appropriate place...).
>
>
>  --
>  (me-tv:28451): GLib-WARNING **: Invalid UTF-8 passed to g_io_channel_write_chars().
>  https://bugs.launchpad.net/bugs/197745
>  You received this bug notification because you are a bug assignee.
>

-- 
(me-tv:28451): GLib-WARNING **: Invalid UTF-8 passed to g_io_channel_write_chars().
https://bugs.launchpad.net/bugs/197745
You received this bug notification because you are a member of Me TV
Development, which is subscribed to Me TV.

Status in Me TV, it's TV for me computer: Fix Released

Bug description:
Me TV-Message: 02.03.2008 20:47:52 - Me TV Version: 0.5.23
Me TV-Message: 02.03.2008 20:47:52 - Chargement du fichier glade '/usr/share/me-tv/glade/me-tv.glade' en cours
Me TV-Message: 02.03.2008 20:47:52 - Création du GEP dans '/home/cpa/.me-tv/epg.xml'
Me TV-Message: 02.03.2008 20:47:52 - GEP chargé
Me TV-Message: 02.03.2008 20:47:53 - Fichier de chaînes chargé
Me TV-Message: 02.03.2008 20:47:53 - Utilisation du moteur 'xine'

(me-tv:28451): GLib-WARNING **: Invalid UTF-8 passed to g_io_channel_write_chars().

(me-tv:28451): GLib-WARNING **: Illegal sequence due to partial character at the end of a previous write.

Me TV-Message: message d'exception: 'Failed to write to channel: 'Séquence d'octets non valide en entrée du convertisseur''

(me-tv:28451): Me TV-CRITICAL **: Impossible d'écrire de le fichier de log: Failed to write to channel: 'Séquence d'octets non valide en entrée du convertisseur'
Me TV-Message: 02.03.2008 20:47:55 - Demande de changement de chaîne dans 'TF1'
Me TV-Message: 02.03.2008 20:47:55 - Changement de chaîne vers 'TF1'
Me TV-Message: 02.03.2008 20:47:55 - Purge des événements restant dans le GEP
Me TV-Message: 02.03.2008 20:47:55 - Evénements du GEP purgés
Me TV-Message: 02.03.2008 20:47:55 - Réglage du transpondeur à 498167000
Me TV-Message: 02.03.2008 20:47:55 - En attente du blocage du signal
Me TV-Message: 02.03.2008 20:47:56 - Signal Bloqué
Me TV-Message: 02.03.2008 20:47:56 - Transpondeur réglé à 498167000
Me TV-Message: 02.03.2008 20:47:56 - Thread de vidéo créé
Me TV-Message: 02.03.2008 20:47:56 - En train d'ouvrir FIFO 'fifo://home/cpa/.me-tv/video.fifo'
Me TV-Message: 02.03.2008 20:47:56 - Processus de flux créé
Me TV-Message: 02.03.2008 20:47:56 - Processus GEP créé

(me-tv:28451): GLib-WARNING **: Invalid UTF-8 passed to g_io_channel_write_chars().

(me-tv:28451): GLib-WARNING **: Illegal sequence due to partial character at the end of a previous write.

Me TV-Message: message d'exception: 'Failed to write to channel: 'Séquence d'octets non valide en entrée du convertisseur''

(me-tv:28451): Me TV-CRITICAL **: Impossible d'écrire de le fichier de log: Failed to write to channel: 'Séquence d'octets non valide en entrée du convertisseur'
Me TV-Message: 02.03.2008 20:47:56 - Essai d'auto-détection des PIDs