Bug 483589 - terminus-font-x11 partially unusable on F-10
Summary: terminus-font-x11 partially unusable on F-10
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: terminus-font
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Hans Ulrich Niedermann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-02 15:26 UTC by Hans Ulrich Niedermann
Modified: 2009-02-24 20:54 UTC (History)
2 users (show)

Fixed In Version: 4.28-1.fc10.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-24 14:39:34 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Hans Ulrich Niedermann 2009-02-02 15:26:47 UTC 
Description of problem:

  On F-10, xterm, xlsfonts, emacs, cannot use the terminus
  font, even though terminus-font-x11 is installed.

Version-Release number of selected component (if applicable):

  terminus-font-x11-4.28-1.fc10.noarch

How reproducible:

  100%

Steps to Reproduce:
1. xlsfonts  | grep terminus
  
Actual results:

  No output.

Expected results:

  A few dozen lines with terminus font names.

Additional info:
Comment 1 Hans Ulrich Niedermann 2009-02-04 15:20:30 UTC 
As I am now actually using F-10 on a day-to-day basis, I will be able to fix this issue.

This might not be fixed in this (old) "terminus-font" package, though, as the package needs to be renamed to fit in with Fedora's new guidelines on naming and packaging fonts.
Comment 2 Hans Ulrich Niedermann 2009-02-18 09:42:58 UTC 
The Gnome terminal (using the new and slow font rendering magic) can use terminus.

emacs and xterm (apparently using the old and quick font rendering magic) cannot.

This gives a better idea as to where to look.
Comment 3 Fedora Update System 2009-02-24 20:54:42 UTC 
terminus-font-4.28-1.fc10.1 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.