After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 739816 - Polari fails to start giving error message "parser error... Failed to parse file"
Polari fails to start giving error message "parser error... Failed to parse f...
Status: RESOLVED DUPLICATE of bug 720179
Product: polari
Classification: Applications
Component: general
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Polari maintainers
Polari maintainers
Depends on:
Blocks:
 
 
Reported: 2014-11-08 13:37 UTC by Atri
Modified: 2014-11-08 13:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Atri 2014-11-08 13:37:06 UTC 
This happens once in a while where polari fails to parse from an irc log file and just refuses to start up as a result. In my opinion, polari should just ignore log files it cannot parse from and start up regardless. Deleting the log file in question allows polari to start again.

Error messages printed to the terminal when polari is started from there are as follows:
-----------------------------------
/home/badshah/.local/share/TpLogger/logs/idle_irc_badshah4001/chatrooms/#suse/20141108.log:563: parser error : xmlParseCharRef: invalid xmlChar value 19

envirmental variable to the current time? I tried ATIME=$(date +%d%m%y%H%M
^
(org.gnome.Polari:2728): tp-logger-WARNING **: Failed to parse file:'/home/badshah/.local/share/TpLogger/logs/idle_irc_badshah4001/chatrooms/#suse/20141108.log'
-----------------------------------
Comment 1 Florian Müllner 2014-11-08 13:47:57 UTC 
We would if we could - unfortunately telepathy-logger does not allow us to deal gracefully with this error and just bails out.
However there is a chance that we are doing something wrong which triggers the log corruption in the first place, so it's still possible that there is a (known) polari issue somewhere ...

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