Matplotlib not able to find basic fonts #17585

Activity

1. anntzer

   added

   topic: text/fonts

   on Jun 6, 2020
2. anntzer commented on Jun 6, 2020

   

   anntzer

   on Jun 6, 2020

   Contributor

   More actions

   Please indicate where Tahoma is installed in your system.
3. anntzer

   added

   status: needs clarificationIssues that need more information to resolve.Issues that need more information to resolve.

   on Jun 11, 2020
4. local-minimum commented on Jul 2, 2020

   

   local-minimum

   on Jul 2, 2020

   More actions

   I'm having the same issue after upgrading code to Python 3.8.2 / mpl v.3.2.1 running in an Ubuntu 20.04 docker image trying to use Utopia font.

   I installed the utopia font via texlive so locations are:

   /usr/share/texlive/texmf-dist/tex/latex/psnfss/utopia.sty
   /usr/share/texlive/texmf-dist/fonts/afm/adobe/utopia
   /usr/share/texlive/texmf-dist/fonts/tfm/adobe/utopia
   /usr/share/texlive/texmf-dist/fonts/type1/adobe/utopia
   /usr/share/texlive/texmf-dist/fonts/vf/adobe/utopia
   /usr/share/texlive/texmf-dist/fonts/map/dvips/psnfss/utopia.map
   

   This didn't produce warnings before upgrade of ubuntu and python.

   >>> from matplotlib import rc
   >>> from matplotlib import pyplot as plt
   >>> rc('font', **{'family': 'serif', 'serif': ['Utopia']})
   >>> fig = plt.figure(None, (20, 20), 120)
   >>> ax = fig.gca()
   >>> ax.set_xlabel('test')
   Text(0.5, 0, 'test')
   >>> fig.savefig('/tmp/test2.png')
   findfont: Font family ['serif'] not found. Falling back to DejaVu Sans.
   
5. tacaswell commented on Jul 2, 2020

   

   tacaswell

   on Jul 2, 2020

   Member

   More actions

   @local-minimum in what version did it used to work?

   Can you removing everything in ~/.cache/matplotlib?

   👍React with 👍3Reacted by Matthew Feickert, 张逸帆 and DooHwan Son
6. QuLogic commented on Jul 2, 2020

   

   QuLogic

   on Jul 2, 2020

   Member

   More actions

   Those paths are for LaTeX; they are not standard paths in which fonts would be found.
7. anntzer commented on Jul 2, 2020

   

   anntzer

   on Jul 2, 2020

   Contributor

   More actions

   There's no real reason why we shouldn't also query them (especially if that's something that can be somewhat automated with e.g. kpsewhich). However the real problem is that these are Type1 (pfb) fonts, which we don't support (well, we support them for raster/png output but not for vector output because of the reliance on ttconv) and therefore it makes sense not to have them (for now) in the cache. To be revisited once ttconv is a thing of the past :)
8. local-minimum commented on Jul 3, 2020

   

   local-minimum

   on Jul 3, 2020

   More actions

   Thanks for the clarification, might or might not be related to the OP though, but for me, I agree that it makes sense and I guess something changed with ubuntu and what fonts are included how.
9. sesise0307 commented on Aug 18, 2020

   

   sesise0307

   on Aug 18, 2020

   More actions

   @local-minimum in what version did it used to work?

   Can you removing everything in ~/.cache/matplotlib?

   It helped me. Thanks!
10. jklymak commented on Sep 7, 2020

    

    jklymak

    on Sep 7, 2020

    Member

    More actions

    This looks to be resolved for the responsive commenters. If there is still an issue we can re-open if more info is provided...
11. jklymak

    closed this as completedon Sep 7, 2020
12. matthewfeickert commented on Jan 8, 2021

    

    matthewfeickert

    on Jan 8, 2021

    Contributor

    More actions

    Can you removing everything in ~/.cache/matplotlib?

    Removing the full cache has proven to be very helpful (for me) for debugging things like this. Is there a way to clean the full cache using the matplotlib API similar to how

    import matplotlib.font_manager
    matplotlib.font_manager._rebuild()

    rebuilds the full font-list cache at ~/.cache/matplotlib/fontlist-v330.json?