Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Experiencing the same problem (described bellow) in gitk package on CentOS7, so maybe RHEL7 is also affected.
$ yum info gitk
Name : gitk
Arch : noarch
Version : 1.8.3.1
Release : 6.el7_2.1
Size : 587 k
Repo : installed
From repo : base
Summary : Git revision tree visualiser
URL : http://git-scm.com/
Licence : GPLv2
Description : Git revision tree visualiser.
Traceback on CentOS7:
Error in startup script: failed to allocate font due to internal system font engine problem
(default value for "-font" in widget ".___tk_set_palette.button")
invoked from within
"$q .___tk_set_palette.$q"
(procedure "tk_setPalette" line 82)
invoked from within
"tk_setPalette background $c selectColor $selc"
(procedure "setui" line 8)
invoked from within
"setui $uicolor"
(file "/usr/bin/gitk" line 11931)
From gitk installation (installed by yum from base repo):
Running transaction
Installing : libXrender-0.9.8-2.1.el7.x86_64
Installing : libXft-2.3.2-2.el7.x86_64
Installing : 1:tcl-8.5.13-8.el7.x86_64
Installing : 1:tk-8.5.13-6.el7.x86_64
Installing : gitk-1.8.3.1-6.el7_2.1.noarch
+++ This bug was initially created as a clone of Bug #811896 +++
Description of problem:
Installing gitk on a bare system to run it over ssh results in a failure to load the proper fonts.
Essentially the whole X client side dependencies are not specified as a requirement.
Version-Release number of selected component (if applicable):
gitk-1.7.10-1.fc17.noarch
How reproducible:
Always
Steps to Reproduce:
1. ssh -Y 192.168.X.Y
2. yum install gitk
3. gitk --all
Actual results:
Error in startup script: failed to allocate font due to internal system font engine problem
(default value for "-font" in widget ".___tk_set_palette.button")
invoked from within
"$q .___tk_set_palette.$q"
(procedure "tk_setPalette" line 82)
invoked from within
"tk_setPalette background $c selectColor $selc"
(procedure "setui" line 8)
invoked from within
"setui $uicolor"
(file "/bin/gitk" line 11673)
Expected results:
gitk window on local machine
Additional info:
n/a
--- Additional comment from Carlo de Wolf on 2012-04-12 05:55:00 EDT ---
The following package install makes the problem go away:
- dejavu-sans-fonts
--- Additional comment from Fedora End Of Life on 2013-07-03 17:16:11 EDT ---
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--- Additional comment from Fedora End Of Life on 2013-07-31 18:14:39 EDT ---
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
I have tried that on clean installation of RHEL 7 Server system and everything works as expected. Only missing package there it is xorg-x11-xauth to make X11 forwarding possible. But that's not problem related to the Git.