Bug 1218943
| Summary: | Segmentation fault | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Prashant <pspatil4u> |
| Component: | tk | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED ERRATA | QA Contact: | Ondřej Lysoněk <olysonek> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | jkejda, pspatil4u, yruseva |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | tk-8.5.13-5.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, TK did not handle fonts correctly and applications using TK could become unresponsive if they did not have the correct fonts installed. TK has been fixed to handle cases when no fonts are installed and such applications no longer crash in this situation.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 12:48:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Prashant
2015-05-06 09:02:23 UTC
not libfonts, thats a java app unrelated to fontconfig Thanks for the update When I ran gitk command inside code repository, I got Segmentation fault on screen and segfault at 37435d661 ip 00007fc5b406c80d sp 00007fff6730b968 error 4 in libfontconfig.so.1.7.0[7fc5b4051000+3a000] in /var/log/messages. I have installed xorg-x11-xauth xterm packages to view my repository code. however gitk run with same configuration in centos6.* vesion. backtrace please? Issue has been resolved after installation yum install xorg-x11-fonts-* package. Thanks Akira and Caolan. This seems happens when no fonts installed. and the real cause was, tk gives an invalid pointer to fontconfig. see Bug#1229991. Reassigning to tk. 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. https://rhn.redhat.com/errata/RHBA-2015-2407.html |