# Set as default mono font
gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"
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?)
For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it no longer works.
The font is 'Dina', from here: www.dcmembers. com/jibsen/ download/ 61/?unapproved= 504&moderation- hash=f1abb9d89c aafa881dcfc05cd 32372e7
http://
I have always installed it using a script:
# install dina fonts/Dina fonts/Dina Dina.zip
sudo mkdir -p /usr/share/
cd /usr/share/
sudo unzip ~/Downloads/
# enable bitmap fonts conf.d/ 70-no-bitmaps. conf
sudo rm -f /etc/fonts/
# rebuild the cache
fc-cache -f -v
# Set as default mono font desktop. interface monospace-font-name "Dina 8"
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?)
I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: /bugs.launchpad .net/ubuntu/ +source/ gnome-font- viewer/ +bug/1375819
https:/
(the window displays but immediately locks up.)
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:
( avail/70- yes-bitmaps. conf
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