Bug 110290
Summary: | Latest glibc update breaks gnome/X | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | John Ketchum <johnk> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | fweimer, lare |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-25 21:03:12 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: |
Description
John Ketchum
2003-11-17 22:52:11 UTC
I had the exact same thing happen on one of my systems. Three others are not exhibiting any difficulty, but I had to do the same workaround on the affected system. One precursor (maybe) that I noticed on the affected system occurred after patch installation: Starting OpenOffice.org ... /usr/lib/openoffice/program/soffice.bin: relocation error: /usr/lib/openoffice/program/libvcl641li.so: undefined symbol: FT_Set_Hint_Flags Ngnome-calculator: relocation error: /usr/lib/libXft.so.2: undefined symbol: FT_Set_Hint_Flags Once I reinstalled the previous glibc version, these errors disappeared as well. We definitely have never heard about any issues like that with any of the updates. People would have complaint a lot. The FT_Set_Hint_flags thing points to freetype. Maybe an incompatibility in the versions you were using. It might be that the problem was previously hidden by a bug in glibc, but if the new version says the symbol is missing, I trust that. You can see for yourself, run readelf -s /usr/lib/freetype.so | fgrep FT_Set_Hint_Flags I'll close the bug shortly unless substantial evidence is shown that there is something wrong in *today's* glibc code. Most compatibility problems attributed to glibc are bugs in applications which are exposed by glibc. Closing the bug. No response received and it seems to be unrelated to glibc in any case. |