[Pidgin] #8106: failure to parse all xml files except prefs.xml at startup

[Pidgin]

#8106: failure to parse all xml files except prefs.xml at startup
-----------------------+----------------------------------------------------
 Reporter:  johnlumby  |        Owner:           
     Type:  defect     |       Status:  new      
Milestone:             |    Component:  libpurple
  Version:  2.5.3      |   Resolution:           
 Keywords:             |  
-----------------------+----------------------------------------------------

Comment(by johnlumby):

 Thanks for the response.

 Re pidgin does not use perl to parse xml  -  I'll take your word for it
 but then why does
 ./configure spit this out?
 checking for perl... /usr/local/bin/perl
 checking for XML::Parser... ok

 If that isn't perl xml-parsing then it sure looks like it.     Could this
 somehow be a clue as to my problem??
 I've included my config.status and config.log in the tar file.

 Re your questions, yes that is exactly what it does.    Starting from no
 user setup or xml files,
 I create an account, which is fine, quit, and on next startup it tells me
 error reading blist.xml
 and the debug log shows error reading all the xml's that are parsed using
 the
 parser-formerly-called-XML::Parser  (i.e. prefs.xml is ok)

 This time I did as you said and did nothing else, didn't set prefs, and
 also turned off auto-login
 so that it would not try to get any contacts.    I've attached a gzipd tar
 like so with names
 hopefully self-explanatory.  (I addedf one extra step -  during failed
 run):

 ticket8106/
 ticket8106/during_firstrun/
 ticket8106/during_firstrun/accounts.xml
 ticket8106/during_firstrun/blist.xml
 ticket8106/during_firstrun/prefs.xml
 ticket8106/during_firstrun/status.xml
 ticket8106/after_firstrun/
 ticket8106/after_firstrun/accounts.xml
 ticket8106/after_firstrun/blist.xml
 ticket8106/after_firstrun/prefs.xml
 ticket8106/after_firstrun/status.xml
 ticket8106/after_firstrun/pidgin.debug.log
 ticket8106/during_failed_run/
 ticket8106/during_failed_run/accounts.xml
 ticket8106/during_failed_run/blist.xml
 ticket8106/during_failed_run/prefs.xml
 ticket8106/during_failed_run/status.xml
 ticket8106/during_failed_run/accounts.xml~
 ticket8106/during_failed_run/blist.xml~
 ticket8106/during_failed_run/status.xml~
 ticket8106/during_failed_run/pidgin.debug.log
 ticket8106/after_fail_and_backup/
 ticket8106/after_fail_and_backup/accounts.xml
 ticket8106/after_fail_and_backup/blist.xml
 ticket8106/after_fail_and_backup/prefs.xml
 ticket8106/after_fail_and_backup/status.xml
 ticket8106/after_fail_and_backup/accounts.xml~
 ticket8106/after_fail_and_backup/blist.xml~
 ticket8106/after_fail_and_backup/status.xml~
 ticket8106/after_fail_and_backup/pidgin.debug.log
 config.log
 config.status

 Re adding a test, thanks for the invitation, but since I clearly don't
 even know
 how pidgin is doing its xml parsing, I doubt I could come up with one.
 What I was hoping was if someone who implemented it could construct a test
 of
 whatever thing it is that pidgin relies on to do the xml parsing,
 maybe parse some incredibly simple xml file to stdout
 using that same interface, and check the rc/output.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/8106#comment:5>
Pidgin <http://pidgin.im>
Pidgin