Opened 12 years ago

Last modified 6 years ago

#767 new defect

Error reading blist.xml

Reported by: frost_ Owned by: elb
Milestone: Component: libpurple
Version: 2.0 Keywords: blist
Cc: mcepl

Description

I'm using beta 7, and it also appears in 2.0, I'm on Vista Ultimate

Attachments (2)

debug.3.log (86.8 KB) - added by Meetloaf 11 years ago.
pidgin-debug.log (12.3 KB) - added by mad_goldfish 11 years ago.

Download all attachments as: .zip

Change History (30)

comment:1 Changed 12 years ago by lschiere

  • Component changed from pidgin (gtk) to winpidgin (gtk)
  • Owner set to datallah
  • pending changed from 0 to 1

What is the text of the error?

comment:2 Changed 12 years ago by frost_

  • pending changed from 1 to 0

error loading blist.xml

comment:3 Changed 12 years ago by datallah

  • pending changed from 0 to 1

We're going to need more information than that, please follow the instructions here for obtaining a debug log.

comment:4 Changed 12 years ago by frost_

  • pending changed from 1 to 0

ok, I downloaded the debug version and uploaded the debug.log if its any help you can check this screenshot of the error I'm getting.

http://img157.imageshack.us/img157/2973/sampleerrorcl3.jpg

comment:5 Changed 12 years ago by datallah

  • pending changed from 0 to 1

Your debug log doesn't contain nearly enough information to be useful, please attach the whole debug log - we really what appears in it at the time the error message comes up.

comment:6 Changed 12 years ago by frost_

  • pending changed from 1 to 0

that appears whenever I start pidgin, and that's the debug I only get

comment:7 Changed 12 years ago by frost_

I suspect that it has something to do with permission, where blist.xml can't be read by pidgin

comment:8 Changed 12 years ago by frost_

ok, this debug log contains "util: Error parsing file"

I think this is the error I'm getting on startup, error reading blist.xml

comment:9 Changed 12 years ago by datallah

  • pending changed from 0 to 1

Can you attach the C:\Users\Swabelicious\AppData\Roaming\.purple\blist.xml~ file.

If you don't want to post it here, you can email it to me directly.

comment:10 Changed 12 years ago by frost_

  • pending changed from 1 to 0

what's your email?

comment:11 Changed 12 years ago by datallah

This was caused by an ICQ buddy alias that contained invalid utf-8 text. I'm waiting to hear back how the alias got set (apparently it is coming from the server).

comment:12 Changed 12 years ago by lschiere

  • Component changed from winpidgin (gtk) to libpurple
  • Milestone set to 2.0.3
  • Owner datallah deleted

comment:13 Changed 12 years ago by seanegan

  • Milestone changed from 2.0.3 to 2.1.0

Milestone 2.0.3 deleted

comment:14 Changed 12 years ago by seanegan

  • Owner set to elb

Ethan, can you trace through the ICQ alias path and make sure it gets validated UTF-8?

comment:15 Changed 11 years ago by Sim-on

  • priority changed from minor to major

I closed #4756, #3897, #3849 and #4610 (includes some more debug-outputs) as duplicates of this...

comment:16 follow-up: Changed 11 years ago by Meetloaf

Hello, I am getting this error as well. Funny this is, I had this error 6 mos agao, and then after a clean install, it never happened (the last version I was running was Pidgin 2.2). I just did a clean install of my system again and this problem appeared with 2.2 with the latest Pidgin build (2.4.1). I attached my debug.log, it's happening the the file is being parsed for some reason.

If I delete the blist.xml file and THEN start pidgin, I do not get the error. Any subsequent start of Pidgin yields the error, until I delete the blist.xml file.

Vista Ultimate x64 SP1 4GB Ram Dell Vostro 1500

Hopefully my log helps.

Thanks.

Changed 11 years ago by Meetloaf

comment:17 in reply to: ↑ 16 Changed 11 years ago by datallah

Replying to Meetloaf:

If I delete the blist.xml file and THEN start pidgin, I do not get the error. Any subsequent start of Pidgin yields the error, until I delete the blist.xml file.

Which protocols are you using? What does the debug log say?

Changed 11 years ago by mad_goldfish

comment:18 Changed 11 years ago by mad_goldfish

I'm getting the same error on Ubuntu 8.04 with Pidgin 2.4.1. Log attached.

I've got accounts on Jabber (including GTalk), Yahoo, MSN and MySpaceIM, but these problems have existed since before I added the MSN and MySpace? accounts, and the plugins shown in the log.

In response to datallah, the culprit appears to be a bad character in the blist.xml file, which is also reported to the console as:

(21:58:23) util: Writing file blist.xml to directory /home/can/.purple (21:58:23) util: Writing file /home/can/.purple/blist.xml (21:58:25) nautilus: don't save blist online. No change (21:58:27) Gtk: Failed to set text from markup due to error parsing markup: Error on line 1: Character reference '5' does not encode a permitted character (21:58:27) Gtk: Failed to set text from markup due to error parsing markup: Error on line 1: Character reference '5' does not encode a permitted character

I believe this line in the blist.xml~ file may be the culprit:

<group name='u&#x5;Chat Friends'>

Which is taken from my Yahoo Messenger list. The other Yahoo groups do not appear to have any entity escapes, and as far as my Windows and web-based Yahoo clients are telling me, the group name is "Chat Friends".

comment:19 Changed 11 years ago by selth

Bug is present on fedora using a 2.4.3-1.fc9

comment:20 Changed 11 years ago by selth

after looking at the xml file, the faulty line comes from an AIM entry :

<setting name='switchspell' type='string'>D����� 2</setting>

comment:21 Changed 11 years ago by elb

selth, that error is most likely caused by the switchspell plugin. You should probably report that to the authors.

In the meantime, you can safely remove that line from your blist.xml while Pidgin is not running, and the problem may go away (if it does not occur elsewhere, as well).

Folks, I'm not really the one to be handling this -- it doesn't look like the Oscar plugin has incoming alias problems (at least, not any more). I think the ultimate problem we need to fix has to do with XML parser robustness. Would anyone like to look at that? (Sadrul?)

comment:22 Changed 11 years ago by selth

If I can make a suggestion... if you enforce the way the settings are written in the file, less problems will occur.

comment:23 Changed 10 years ago by frost_

please delete my debug logs

comment:24 Changed 8 years ago by thecondordb

I can confirm this error. Running Ubuntu 10.04 (64 Bit) with Linux 2.6.32-25-generic #44-Ubuntu, Gnome 2.30.2 and Pidgin 2.7.3 here.

The error »error reading blist.xml« happened to me the first time and when executing »xmllint blist.xml~«, in my ~/.purple directory, I get the following information:

* snip * blist.xml~:32: parser error : xmlParseCharRef: invalid xmlChar value 29 <setting name='core-rlaager-irchelper_topic' type='string'>&#x1d;Welkom op d ... etc. etc. * snip *

If I manually remove the »&#x1d;« from the corresponding line in the blist.xml file, Pidgin starts normally.

Please, who can fix this? If You don't feel responsible, where should this bug be reported instead and against what package?

Thank You.

Dennis

comment:25 follow-up: Changed 8 years ago by Miram

Running Vista 32 bit and Pidgin 2.7.1, like thecondordb I manually removed the offending UTF characters from my blist.xml file and everything works fine now.

The characters were displayed as part of the topic of an IRC channel I have added, and if I return, the characters are stored in blist.xml again and I get the error all over again. Does anyone know what I could do about this? Thanks.

comment:26 in reply to: ↑ 25 ; follow-up: Changed 8 years ago by elb

Replying to Miram:

The characters were displayed as part of the topic of an IRC channel I have added, and if I return, the characters are stored in blist.xml again and I get the error all over again. Does anyone know what I could do about this? Thanks.

Ah hah! Another actual data point to work with!

A few questions:

  1. Does this happen only when the irc-helper plugin is loaded (I suspect so)?
  2. What is the specific topic which causes this problem?

I suspect there are two things going on here; one, we have disagreement between the blist.xml writing and reading on how to encode non-ASCII characters (or even if they have to be encoded), and two, a third-party plugin which is writing non-UTF-8 data to the blist somehow.

comment:27 in reply to: ↑ 26 Changed 8 years ago by Miram

Replying to elb:

A few questions:

  1. Does this happen only when the irc-helper plugin is loaded (I suspect so)?
  2. What is the specific topic which causes this problem?

This only happens when IRC Helper is enabled, and "&#x1d;" is the character at fault.

comment:28 Changed 6 years ago by vegivamp

And another instance :-)

For me, the offending line is "<setting name='lastsaid' type='string'>is away: (afk) [&#x2;BX&#x2;-MsgLog? On]</setting>", and comes from an IRC contact's auto-away.

Pidgin 2.10.3 on Linux Mint Maya 64-bit. I do *not* have IRC-helper enabled. I do have "IRC More" enabled, as well as Album, Buddy Notes, Conversation Badger, difftopic, Extended Preferences, History, Last Seen, Markerline, Message Notification, NickSaid? and Off-the-Record Messaging.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!