Bug 160737 - x3270-x11 rpm has corrupt fonts(3270*).
x3270-x11 rpm has corrupt fonts(3270*).
Product: Fedora
Classification: Fedora
Component: x3270 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Karsten Hopp
: 163923 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2005-06-16 19:30 EDT by Jonathan Claxton
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-20 08:13:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jonathan Claxton 2005-06-16 19:30:29 EDT
Description of problem, bug, incorrect information, or enhancement request:

Installed x3270-x11 rpm... tried to use x3270 with a font size, got a message
saying "Font is not availible..." or words to that effect. 

Did a LOT of digging, finally did a ls -al /usr/X11R6/lib/X11/fonts/misc/3270*,
every one of the fonts has a size of 20 where the real ones are bigger. Had the
old fc3 partition that I use to copy the real ones over to the FC4 and now x3270
finds the fonts.
Comment 1 Jonathan Claxton 2005-07-14 13:01:38 EDT
I just downloaded the .src.rpm that builds this x3270-x11 and did a rpm -ba of
the spec file and the resultant x3270-x11 .rpm file has the correct fonts. 

Sounds like someone needs to do a rebuild of the rpm to make sure that it has
the correct fonts in it. 

Comment 2 Karsten Hopp 2005-07-20 08:13:31 EDT
That's caused by a missing 'BuildRequires: xorg-x11-font-utils'
fixed in the next version
Comment 3 Karsten Hopp 2005-07-22 16:49:15 EDT
*** Bug 163923 has been marked as a duplicate of this bug. ***
Comment 4 Jonathan Claxton 2005-07-28 14:26:27 EDT
Just got the new x3270-x11 rpm update and installed it. Checked to make sure it
has the fonts and it does. Loaded the x3270 app and it finds the fonts. 


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