After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 398567 - undefined symbol: libxml_xmlDocPtrWrap
undefined symbol: libxml_xmlDocPtrWrap
Product: GStreamer
Classification: Platform
Component: gst-python
Other Linux
: High normal
: 0.10.8
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 473234 (view as bug list)
Depends on:
Blocks: 607313
Reported: 2007-01-19 23:39 UTC by Brendan Howell
Modified: 2017-07-26 17:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Test pygst xml output (167 bytes, text/plain)
2007-03-02 04:23 UTC, Brendan Howell
gst: avoid unresolved xml symbol (1.21 KB, patch)
2011-05-28 20:45 UTC, Mark Nauwelaerts
rejected Details | Review

Description Brendan Howell 2007-01-19 23:39:40 UTC
calling "gst.xml_write(element)"

gives the following output:

python: symbol lookup error: /usr/lib/python2.4/site-packages/gst-0.10/gst/ undefined symbol: libxml_xmlDocPtrWrap
Comment 1 Stefan Sauer (gstreamer, gtkdoc dev) 2007-03-01 08:56:28 UTC
Does this still happen? Which version of libxml have you installed?
Comment 2 Brendan Howell 2007-03-02 04:23:11 UTC
Created attachment 83709 [details]
Test pygst xml output
Comment 3 Brendan Howell 2007-03-02 04:26:22 UTC
It's still happening and I've tested it on Ubuntu Feisty with the latest updates.  It's using libxml2 2.6.27.  The above test case demonstrates.
Comment 4 Edward Hervey 2007-03-02 10:22:20 UTC
Really critical indeed.

So that symbol is contained in the libxml2 python module (site-packages/
It is defined as extern in the gst module, but for some reason when it tries to resolve that symbol after the libxml2 python module is loaded.. it fails.

I'm wondering if this is REALLY the best way to do that.
Comment 5 Edward Hervey 2007-03-02 11:03:56 UTC
The problem was that the libxml2 module was being loaded without GLOBAL and LAZY flags.

2007-03-02  Edward Hervey  <>

	* gst/
	Import libxml2 (if available) at import time with GLOBAL and LAZY flags.
	Fixes #398567

Comment 6 Yaakov Selkowitz 2007-05-01 05:57:43 UTC
This doesn't help for Cygwin or MinGW, as the undefined symbol causes the *link* to fail.  Patching gst/ doesn't help; another way needs to be found to import required libxml2 code without using its symbols.  While many python modules depend on others, pygtk included, not one does so in the way done here.

Please reopen.
Comment 7 David Schleef 2009-08-14 05:40:21 UTC
Repoening.  Same comment as previous.
Comment 8 David Schleef 2009-11-07 00:26:28 UTC
*** Bug 473234 has been marked as a duplicate of this bug. ***
Comment 9 Edward Hervey 2009-11-07 08:45:30 UTC
Any suggestions on how to fix this ? Or rather (question to the cygwin ports maintainer), any pointers to python packages with the same goals, but doing it differently ?
Comment 10 Yaakov Selkowitz 2009-11-08 01:24:43 UTC
How about something similar to the xmlNodePtrWrap handling in
Comment 11 Edward Hervey 2009-11-16 08:02:30 UTC
Cygwin maintainers: We are handling it exactly the same way as xmlNodePtrWrap in

Could you attach the config.log, config.h and generated gst/gst.c ?
Comment 12 Stefan Sauer (gstreamer, gtkdoc dev) 2010-08-10 07:27:55 UTC
Is this still an issues?
Comment 13 Yaakov Selkowitz 2010-08-10 08:02:29 UTC
Comment 14 Mark Nauwelaerts 2011-05-28 20:45:26 UTC
Created attachment 188815 [details] [review]
gst: avoid unresolved xml symbol

This is one way to 'fix' this.  That is, it least it allows building gst-python form mingw and cygwin, at the expense of a non-functional gst_xml_write wrapper, which is hardly a great loss and provides a whole more gst-python for e.g. cygwin than currently (= none, out-of-the-box).
Comment 15 Sebastian Dröge (slomo) 2012-12-17 11:34:00 UTC
Closing this bug now, gst-python is only an extension module to pygi now and this bug doesn't make much sense anymore in this context.
Comment 16 Ivan Zakharyaschev 2017-07-26 17:55:43 UTC
A similar bug report, but with less information: