In short, the problem is that the apparmor profile for evince does not allow the font files to be written.
Unfortunately, the algorithm used by the TeXLive scripts to decide where to write generated font files is complicated. For example, in my case, they seem to be written under
$HOME/texmf/fonts
but I also have files generated in the recent past (perhaps with a previous version of TeXLive?) under $HOME/.texmf-var/fonts
and there are other possibilities, I believe. Hence, finding a solution that is both secure and reliable requires input from a TeXpert.
For the moment I have simply disabled Evince's apparmor profile.
This bug appears to be the problem reported here: http:// ubuntuforums. org/showthread. php?p=8690020
In short, the problem is that the apparmor profile for evince does not allow the font files to be written.
Unfortunately, the algorithm used by the TeXLive scripts to decide where to write generated font files is complicated. For example, in my case, they seem to be written under
$HOME/texmf/fonts
but I also have files generated in the recent past (perhaps with a previous version of TeXLive?) under $HOME/. texmf-var/ fonts
and there are other possibilities, I believe. Hence, finding a solution that is both secure and reliable requires input from a TeXpert.
For the moment I have simply disabled Evince's apparmor profile.