libreport version: 2.0.10 abrt_version: 2.0.10 cmdline: /usr/bin/python /usr/share/system-config-printer/system-config-printer.py executable: /usr/share/system-config-printer/system-config-printer.py kernel: 3.3.4-3.fc17.x86_64 time: lun 14 mai 2012 09:25:53 CEST uid: 1000 username: jeff backtrace: Text file, 7574 bytes
Created attachment 584274 [details] File: backtrace
Thank you for the report. What do the following commands show ? rpm -q python-libs rpm -V python-libs
Hello, rpm -q python-libs python-libs-2.7.3-6.fc17.x86_64 rpm -V python-libs returns nothing
thanks, and what about: python -c 'from pyexpat import *'
python -c 'from pyexpat import *' Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: /usr/lib64/python2.7/lib-dynload/pyexpat.so: undefined symbol: XML_SetHashSalt
What is the output of: rpm -q expat ? This should be fixed in expat-2.1.0 (which is stable for quite some time now)
*** Bug 823296 has been marked as a duplicate of this bug. ***
rpm -q expat expat-2.1.0-1.fc17.x86_64 expat-2.1.0-1.fc17.i686
try ldd /usr/lib64/python2.7/lib-dynload/pyexpat.so I have oracle installed and as a result of LD_LIBRARY_PATH=/opt/oracle/product/11.2.0/db_1/lib it's picking up the wrong expat
try ldd /usr/lib64/python2.7/lib-dynload/pyexpat.so linux-vdso.so.1 => (0x00007fff679ff000) libexpat.so.1 => /home/jeff/app/jeff/product/11.2.0/client_1/lib/libexpat.so.1 (0x00007f6da898e000) libpython2.7.so.1.0 => /lib64/libpython2.7.so.1.0 (0x00007f6da85b3000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f6da8397000) libc.so.6 => /lib64/libc.so.6 (0x00007f6da7fe0000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f6da7ddb000) libutil.so.1 => /lib64/libutil.so.1 (0x00007f6da7bd8000) libm.so.6 => /lib64/libm.so.6 (0x00007f6da78dd000) /lib64/ld-linux-x86-64.so.2 (0x00000032f4200000)
(In reply to comment #9) > try ldd /usr/lib64/python2.7/lib-dynload/pyexpat.so > > I have oracle installed and as a result of > LD_LIBRARY_PATH=/opt/oracle/product/11.2.0/db_1/lib > > it's picking up the wrong expat Thanks for pointing that out! So I guess we cannot resolve this name clash of the library. The only thing expat can do is to bump the SONAME, so it differs from oracle. Reassigning to expat, as XML_SetHashSalt was added without bumping the SONAME anyway, so they can decide to either bump or not.
No. If you set LD_LIBRARY_PATH to a directory containing libraries with the same soname as Fedora system libraries, the behaviour of Fedora binaries is no longer predictable.
*** Bug 829531 has been marked as a duplicate of this bug. ***
I had a duplicate bug opened with precisely the same problem as described here. My workaround was to install the instant client and point my ORACLE_HOME there. Instant client doesn't contain the expat library, so all is well for now.
*** Bug 835548 has been marked as a duplicate of this bug. ***
*** Bug 838366 has been marked as a duplicate of this bug. ***
*** Bug 851195 has been marked as a duplicate of this bug. ***
*** Bug 830597 has been marked as a duplicate of this bug. ***
*** Bug 850983 has been marked as a duplicate of this bug. ***
*** Bug 855610 has been marked as a duplicate of this bug. ***
*** Bug 861998 has been marked as a duplicate of this bug. ***
I'll see if I can add workaround to this from the python side.
Cet incident est survenu depuis que j'ai désactivé le Pare feu Package: system-config-firewall-1.2.29-7.fc17 OS Release: Fedora release 17 (Beefy Miracle)
*** Bug 923391 has been marked as a duplicate of this bug. ***
*** Bug 949920 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.