Bug 1785548

Summary: Fedora 31 cannot use Courier 10 Pitch
Product: [Fedora] Fedora Reporter: lixiaoyi13691419520
Component: fontconfigAssignee: Akira TAGOH <tagoh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 31CC: ajax, caillon+fedoraproject, fonts-bugs, gnome-sig, i18n-bugs, john.j5live, lixiaoyi13691419520, mclasen, pnemade, rhughes, rstrode, sandmann, tagoh
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-24 09:20:23 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 lixiaoyi13691419520 2019-12-20 08:19:27 UTC
Description of problem:
After updating from Fedora 30 to Fedora 31, the Courier 10 Pitch font is no longer available, even if the package xorg-x11-fonts-Type1 is installed and fc-list command shows the font

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


How reproducible:
Always

Steps to Reproduce:
1. Make sure Fedora 31 is available (e.g. use Fedora Live CD)
2. sudo dnf install xorg-x11-fonts-Type1
3. fc-list | grep "Courier 10 Pitch"
   # make sure the font is available in fc-list
4. Open gedit, go to Preferences -> Fonts&Colors -> Edior font
5. Search for "Courier 10 Pitch".

Actual results:
Cannot find font "Courier 10 Pitch"

Expected results:
Can find font "Courier 10 Pitch"

Additional info:
* The font is also not fond on gnome-terminal, LibreOffice Writer, etc.
* Works on Fedora 30 and lower. 
* If update from Fedora 30 to 31, then gnome-terminal and gedit will not be able to find the font, and all characters become a square with some hexadecimal numbers in it, like:
  +--+ +--+
  |00| |00|
  |31| |32|
  +--+ +--+

Comment 1 Akira TAGOH 2019-12-24 09:20:23 UTC

*** This bug has been marked as a duplicate of bug 1779123 ***