RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Latest google chrome browser (v. 28) requires glibc-3.4.15 which is not shipped for RHEL 6. In addition, google doesn't support Chrome v. 27 anymore (not available through google repository). This make it installation of new google chrome impossible on RHEL 6, update is also impossible (as version can't be updated from v27 to v28 because of missing glibc dependencies)

Version-Release number of selected component (if applicable):
Google Chrome v. 28

How reproducible:
Try to install google chrome latest version on RHEL

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

There is no glibc 3.4.15.  Maybe you mean the kernel version 3.4.15?

-> Running transaction check
---> Package google-chrome-stable.x86_64 0:27.0.1453.93-200836 will be updated
---> Package google-chrome-stable.x86_64 0:28.0.1500.71-209842 will be an update
--> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) for package: google-chrome-stable-28.0.1500.71-209842.x86_64
--> Finished Dependency Resolution
Error: Package: google-chrome-stable-28.0.1500.71-209842.x86_64 (google-chrome)
           Requires: libstdc++.so.6(GLIBCXX_3.4.15)(64bit)

That's libstdc++, not glibc.  I don't think we can do anything about this, but I'll let the gcc maintainers close this as wontfix.

Yeah, the only way around this would be convince google to build chrome on RHEL using Developer Toolset, then it would work.  Updating the system libstdc++.so.6 is definitely not an option.