From: shtayerc <shtayerc@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] pdflatex Font not found
Date: Sat, 16 May 2020 16:21:38 +0200 [thread overview]
Message-ID: <20200516142138.M2owRM69B-W7mbPdtMcl05DYf4T2ploUuTdf5lZf3IE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22012@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Closed issue by shtayerc on void-packages repository
https://github.com/void-linux/void-packages/issues/22012
Description:
### System
* xuname:
Void 5.4.41_1 x86_64 GenuineIntel uptodate rrrrmmnFFFFFF
* package:
texlive-bin-2020_1
### Expected behavior
`pdflatex` successfully compiles
### Actual behavior
```
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020) (preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./test.tex
LaTeX2e <2020-02-02> patch level 5
L3 programming layer <2020-05-14>
(/opt/texlive/2020/texmf-dist/tex/latex/base/article.cls
Document Class: article 2019/12/20 v1.4l Standard LaTeX document class
(/opt/texlive/2020/texmf-dist/tex/latex/base/size10.clo))
(/opt/texlive/2020/texmf-dist/tex/latex/l3backend/l3backend-pdfmode.def)
(./test.aux) [1{/opt/texlive/2020/texmf-var/fonts/map/pdftex/updmap/pdftex.map}
] (./test.aux) )
!pdfTeX error: /opt/texlive/2020/bin/x86_64-linux/pdflatex (file tcrm1000): Fon
t tcrm1000 at 600 not found
==> Fatal error occurred, no output PDF file produced!
```
### Steps to reproduce the behavior
Run `pdflatex test.tex`.
Content of test.tex:
```tex
\documentclass{article}
\begin{document}
\begin{itemize}
\item Test
\end{itemize}
\end{document}
```
prev parent reply other threads:[~2020-05-16 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 12:51 [ISSUE] " shtayerc
2020-05-16 13:21 ` Anachron
2020-05-16 13:27 ` flexibeast
2020-05-16 13:32 ` flexibeast
2020-05-16 13:58 ` shtayerc
2020-05-16 14:21 ` shtayerc
2020-05-16 14:21 ` shtayerc [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200516142138.M2owRM69B-W7mbPdtMcl05DYf4T2ploUuTdf5lZf3IE@z \
--to=shtayerc@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).