Description of problem: After upgrading my Fedora 30 XFCE workstation to Fedora 31, my xfce4-terminals that are configured to use LucidaTypewriter Sans font only rectangles instead of letters. Version-Release number of selected component (if applicable): bitmap-lucida-typewriter-fonts-0.3-31.fc31.noarch How reproducible: Deterministic. Steps to Reproduce: 1. Use xfce4-terminal with LucidaTypewriter Sans on Fedora 30. 2. Upgrade to Fedora 31. Actual results: Unreadable. Expected results: Readable. Additional info: On Fedora 31 installation, the LucidaTypewriter Sans font cannot even be selected in terminal's Preferences > Appearance > Font selection.
This seems to be a manifestation of bug 1753295. When I tried to rebuild the bitmap-fonts using the fonttosfnt approach from bug 1753295 comment 4, I get Lucida displayed but the linespaces are increased, making the result unusable. The same problem for Terminus is tracked as bug 1748495.
Please try the following commands: $ fonttosfnt -b -g 2 -m 2 -o lucidab.otb ../bitmap-lucida-typewriter-fonts/lutBS*.pcf.gz $ fonttosfnt -b -g 2 -m 2 -o lucidar.otb ../bitmap-lucida-typewriter-fonts/lutRS*.pcf.gz
Created attachment 1637784 [details] Original LucidaTypewriter with pango downgraded to pango-1.43.0-4.fc30
Created attachment 1637788 [details] LucidaTypewriter converted to OTB using fonttosfnt with pango-1.44.7-1.fc31
I've now attached screenshots showing what the original PCF font looks like with Pango from Fedora 30, and how with new Pango in Fedora 31 and fonts converted to OTB using commands from comment 2 have extra line spacing.
What is that "Terminal" software you are showing in those screenshots?
I'm using xfce4-terminal.
The issue is still present on Fedora 32 with pango-1.44.7-3.fc32.
Installing bitmap-lucida-typewriter-opentype-fonts-0.3-33.fc32.noarch instead of the non-opentype package makes the letters in the terminal show up. However, there is an extra white space between lines, making the terminal space wasted and basically unusable.
Tomáš has reported the spacing problem in bug 1839471. So I guess this bugzilla could be closed as CURRENTRELEASE because some fix happened, and the spacing problem tracked in bug 1839471.
Okay, close bug now.