Hide Forgot
+++ This bug was initially created as a clone of Bug #557651 +++ ====================================== Description of problem: Got the above error message when I run Google Chrome or any other application that requires version information in libz.so.1. I am submitting in regard to libz.so.1 without version information available, but not the difficulties of using chrome. Users should have same error if they run an application that requires version information on libz.so.1 Version-Release number of selected component (if applicable): zlib-1.2.3-26.el6.x86_64 How reproducible: Always. Steps to Reproduce: 1. Install RHEL 6. 2. Install all packages needed. 3. Install Google Chrome from a 3rd party repo. 3. Start Google Chrome. It starts with the error message: /lib64/libz.so.1: no version information available Additional info: N/A +++++++++++++++++++original bug comments++++++++++++++++++++++++++++++++ --- Additional comment from jh.redhat on 2010-02-12 04:58:04 EST --- google-chrome-beta-5.0.307.7-38400.x86_64 at least doesn't crash any more, but the error message ist still there. This is probably the same problem as in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431124, the fix sounds to be quite small. --- Additional comment from caius.chance on 2010-02-14 19:41:03 EST --- If you could kindly patch it on Fedora that would be fantastic. if you decide to let be then that's alright. Thanks very much for your help. --- Additional comment from varekova on 2010-03-31 09:45:38 EDT --- Thanks, fixed in zlib-1.2.4-1.fc14. --- Additional comment from felipe.contreras on 2010-06-16 13:49:26 EDT --- What would be needed to get this on F13? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0398.html