Bug 111469 - redhat-config-packages all others in system-settings do not work
redhat-config-packages all others in system-settings do not work
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-packages (Show other bugs)
9
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Jeremy Katz
David Lawrence
http://rahall@sbcglobal.net
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-12-03 20:26 EST by Robert Hall
Modified: 2007-03-27 00:12 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-12-10 02:03:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Robert Hall 2003-12-03 20:26:04 EST
Description of problem:
The following message is sent when I try to run redhat-config-packages:
python: relocation error: /usr/local/lib/libpng12.so.0: undefined
symbol: inflateInit_

Version-Release number of selected component (if applicable):
Redhat 9_0

How reproducible:
Happens every time!!

Steps to Reproduce:
1.System Settings
2.Add/Remove Applications (or other choice in this menu)
3.
  
Actual results:
Window does not come up!!

Expected results:


Additional info:
System is completely up to date!! I looked at dependencies for the
redhat-config-packages and force installed all packages. Results
stayed the same!
Comment 1 Jeremy Katz 2003-12-03 20:53:45 EST
Can you run `rpm -V libpng`?  
Comment 2 Robert Hall 2003-12-03 23:07:19 EST
Yes, I can with no errors!
Comment 3 Robert Hall 2003-12-05 14:28:16 EST
Is anyone working on this bug?  I haven't heard anything since the Dec 3?
Comment 4 Jeremy Katz 2003-12-10 02:03:55 EST
I see what it is.. you have a broken install of libpng in
/usr/local/lib -- remove that and your problem should go away.
Comment 5 Robert Hall 2003-12-10 11:18:28 EST
Thanks!!!

Note You need to log in before you can comment on or make changes to this bug.