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.
Bug 1218943 - Segmentation fault
Summary: Segmentation fault
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tk
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: Ondřej Lysoněk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-06 09:02 UTC by Prashant
Modified: 2015-11-19 12:48 UTC (History)
3 users (show)

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.
Clone Of:
Environment:
Last Closed: 2015-11-19 12:48:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2407 0 normal SHIPPED_LIVE tk bug fix update 2015-11-19 11:11:31 UTC

Description Prashant 2015-05-06 09:02:23 UTC
Description of problem: Not able to open Xwindow applications.


Version-Release number of selected component (if applicable): libfontconfig.so.1.7.0


How reproducible: try to run any x window depending app


Steps to Reproduce:
1.
2.
3.

Actual results:
ernel: wish[28767]: segfault at 37435d661 ip 00007fc5b406c80d sp 00007fff6730b968 error 4 in libfontconfig.so.1.7.0[7fc5b4051000+3a000]

Expected results:


Additional info:

Comment 2 Caolan McNamara 2015-05-06 09:22:17 UTC
not libfonts, thats a java app unrelated to fontconfig

Comment 3 Prashant 2015-05-06 14:34:43 UTC
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.

Comment 4 Akira TAGOH 2015-05-07 02:33:22 UTC
backtrace please?

Comment 5 Prashant 2015-05-07 03:55:06 UTC
Issue has been resolved after installation yum install xorg-x11-fonts-* package.

Thanks Akira and Caolan.

Comment 6 Akira TAGOH 2015-06-10 05:45:55 UTC
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.

Comment 9 errata-xmlrpc 2015-11-19 12:48:26 UTC
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


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