Bug 461151

Summary:	2.7.1-1 gives pidgin indigestion
Product:	[Fedora] Fedora	Reporter:	Valdis Kletnieks <valdis.kletnieks>
Component:	libxml2	Assignee:	Daniel Veillard <veillard>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	johan-fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-24 18:42:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Valdis Kletnieks 2008-09-04 16:07:33 UTC

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):
libxml2-2.7.1-1.fc10.x86_64.rpm

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
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....

Comment 1 Valdis Kletnieks 2008-10-03 21:26:38 UTC

Problem verified still present in 2.7.1-2.

Comment 2 Daniel Veillard 2008-10-07 15:47:21 UTC

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.

Daniel

Comment 3 Valdis Kletnieks 2008-10-07 16:15:03 UTC

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...

Comment 4 Johan Kok 2008-10-24 17:05:43 UTC

(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.

Comment 5 Valdis Kletnieks 2008-10-24 18:18:25 UTC

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.

Comment 6 Johan Kok 2008-10-24 18:42:02 UTC

Alright. Thanks for checking and good to hear the problem is now resolved.