All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Pango |
Fix Released
|
Unknown
|
|||
pango1.0 (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work.
The font is 'Dina', from here:
http://
I have always installed it using a script:
# install dina
sudo mkdir -p /usr/share/
cd /usr/share/
sudo unzip ~/Downloads/
# enable bitmap fonts
sudo rm -f /etc/fonts/
# rebuild the cache
fc-cache -f -v
# Set as default mono font
gsettings set org.gnome.
This has always worked in the past, through many versions of Ubuntu, including 19.10.
I installed Focal today, using `sudo do-release-upgrade -d`.
Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?)
gnome-font-viewer does not list any of the installed bitmap fonts.
While trying to find a fix, I tried a few changes to the above script, which did not help:
* Unzip to "$HOME/.fonts" instead
* Trying other symlinks in the fonts config.d:
(
cd /etc/fonts/conf.d
sudo rm -f 70-no-bitmaps.conf
sudo ln -sf ../conf.
)
(tried with both 'yes-bitmaps' and 'force-bitmaps')
* fc-cache -r # "really" force cache re-creation
summary: |
- All bitmap fonts no longer visible on upgrade 19.10 -> Focal + All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) |
description: | updated |
description: | updated |
description: | updated |
Changed in pango1.0 (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in pango: | |
status: | Unknown → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1861340/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]