Bug 46045 - Failed to parse logs with binary (invalid xmlChar)
Summary: Failed to parse logs with binary (invalid xmlChar)
Status: RESOLVED DUPLICATE of bug 40675
Alias: None
Product: Telepathy
Classification: Unclassified
Component: logger (show other bugs)
Version: unspecified
Hardware: Other All
: high normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-14 06:59 UTC by Laurent Bigonville
Modified: 2012-04-27 10:12 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Laurent Bigonville 2012-02-14 06:59:15 UTC 
Hi,

Yesterday I've been able to inject binary into the log of one of my conversation and this morning I saw that I cannot get the backlog.


The logs show me that:

/home/bigon/.local/share/TpLogger/logs/gabble_jabber_bigon_40foo_2ebe0/my@contact/20120213.log:202: parser error : xmlParseCharRef: invalid xmlChar value 1
 message-token='0395044b-cf55-4bb0-906e-5c0d128ae778'>retourne 10.0.100.18 
                                                                               ^
/home/bigon/.local/share/TpLogger/logs/gabble_jabber_bigon_40foo_2ebe0/my@contact/20120213.log:202: parser error : xmlParseCharRef: invalid xmlChar value 2
age-token='0395044b-cf55-4bb0-906e-5c0d128ae778'>retourne 10.0.100.18 
                                                                               ^
/home/bigon/.local/share/TpLogger/logs/gabble_jabber_bigon_40foo_2ebe0/my@contact/20120213.log:202: parser error : xmlParseCharRef: invalid xmlChar value 2
4b-cf55-4bb0-906e-5c0d128ae778'>retourne 10.0.100.18 __MSBROWSE__
                                                                               ^

(gnome-shell:2170): tp-logger-WARNING **: Failed to parse file:'/home/bigon/.local/share/TpLogger/logs/gabble_jabber_bigon_40foo_2ebe0/my@contact/20120213.log'
Comment 1 Cosimo Alfarano 2012-04-27 10:12:15 UTC 
being a binary file, g_markup_escape is escaping verbatim the file, but some escaped chars are not valid XML.

THis is the same problem as bug#40675, moving the discussion there.

*** This bug has been marked as a duplicate of bug 40675 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.