Red Hat Bugzilla – Bug 461151
2.7.1-1 gives pidgin indigestion
Last modified: 2008-10-24 14:42:02 EDT
Description of problem:
After upgrading to libxml2 to 2.7.1-1, pidgin fails to connect to Jabber servers, instead throwing a 'xml2 parse error'. Dropping back to libxml2-2.6.32-3.fc10.x86_64 and everything works fine again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This is a self-compiled pidgin pulled from the development monotone repository. If somebody can suggest what instrumentation/debugging printf's to add, I can do that....
Problem verified still present in 2.7.1-2.
no idea what pidgin is doing under the hood, libxml2-2.7.2-1 is out and may
fix the problem ... or not, I have no idea where the problem came from.
Just checked, still busticated at 2.7.2-1. I suspect that pidgin is tripping over some small API change (a number of other RPMs that use libxml2 issue a warning during 'yum update' that they were compiled against 207 but 206 is installed). Complicating matters is that developer.pidgin.im has been down for the last few days, so I can't pull the latest Monotone repository for pidgin and see if it's already fixed upstream...
(In reply to comment #3)
> Complicating matters is that developer.pidgin.im has been down for
> the last few days, so I can't pull the latest Monotone repository for pidgin
> and see if it's already fixed upstream...
Ping. Developer.pidgin.im seems to be responding again. Have you had a moment to check with a new development version to see if this is fixed or what is causing the problem? Thanks.
Yeah, I saw it come back up. I've rebuilt the current MTN version against libxml2 2.7.2-1 and it's working now. Not sure which of the multitudinous commits against the pidgin Jabber support did it.
Alright. Thanks for checking and good to hear the problem is now resolved.