Bug 834203
Summary: | [abrt] kde-printer-applet-4.8.3-1.fc17: expat.py:4:<module>:ImportError: /usr/lib64/python2.7/site-packages/_xmlplus/parsers/pyexpat.so: undefined symbol: XML_SetHashSalt | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | ramindeh | ||||
Component: | PyXML | Assignee: | Roman Rakus <rrakus> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 17 | CC: | jreznik, kevin, ltinkl, rdieter, rnovacek, rrakus, steve.traylen, than, tsmetana | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:c497551e1b46b5dce92e42a83c295db1e3a37eda | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-06-21 23:22:38 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: | |||||||
Attachments: |
|
Description
ramindeh
2012-06-21 08:12:04 UTC
Created attachment 593385 [details]
File: backtrace
It's clearly still a problem with pyexpat (PyXML) on your box, unclear if it's self(oracle) induced or not. * Since Python is a black box to me, I would not know how to find out what is wrong with it * Expat is part of python-devel afaik. Both python-devel and pyxml are installed. * This problem started after an update I made to the system 1-2 days before upgrading to FC17 several days ago, and not when I shoehorned Oracle onto the system about 6 months ago, so I suspect it must be some change in pyexpat Bug 814490 is possibly related to this one. The pyexpat in Fedora moved on, the stale bundled copy in Oracle did not. It's still Oracle's (or your) fault for installing a bundled copy systemwide in the first place. It's perfectly normal and expected for bundled old copies of libraries to conflict with newer system versions. In general, the proper resolution is to delete the bundled version to force the use of the system version everywhere. |