Public bug reported:

Binary package hint: pidgin

Description:    Ubuntu 8.10
Release:        8.10
Pidgin 2.5.2

App started and reported blist.xml was corrupt and was moved to
blist.xml~, all IRC channels were lost from the new blist.xml
configuration file.

Running xmllint on the corrupted blist.xml file returns the following 3 errors 
on line 114:
/home/ged/.purple/blist.xml.20090206:114: parser error : xmlParseCharRef: 
invalid xmlChar value 16
                                <buddy account='&#x10;F&#x10;&#x1;' 
proto='prpl-jabber'>
                                                      ^
/home/ged/.purple/blist.xml.20090206:114: parser error : xmlParseCharRef: 
invalid xmlChar value 16
                                <buddy account='&#x10;F&#x10;&#x1;' 
proto='prpl-jabber'>
                                                             ^
/home/ged/.purple/blist.xml.20090206:114: parser error : xmlParseCharRef: 
invalid xmlChar value 1
                                <buddy account='&#x10;F&#x10;&#x1;' 
proto='prpl-jabber'>

The rest of the file appears to be fine, with all other instances of the
account tag correctly showing my gtalk login id for prpl-jabber protocol
entries.

I don't know how to reproduce this, the last run prior to it happening
was ended when I did a normal system shutdown using the "Shut Down..."
Gnome panel icon.

Let me know if there's any other info I can provide.

-G

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.2-0ubuntu1
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux 2.6.27-7-generic x86_64

** Affects: pidgin (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug

-- 
blist.xml was corrupted during normal shutdown - "buddy" tag "account" 
attribute contains invalid XML chars
https://bugs.launchpad.net/bugs/326425
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to