Arch Linux

Bevan

Member

Registered: 2009-09-08

Posts: 102

[solved] texlive doesn't work correctly, when lmodern is used

Hi!

I've got a problem with texlive: When I use the package lmodern and my document contains mathematical symbols like integrals or sums or special chars like german umlauts, dvips and pdftex give me error messages and the symbols are not displayed correctly in the resulting document.

Here an example .tex-file:

\documentclass{scrartcl}
\usepackage{amsmath}
\usepackage{lmodern}
\begin{document}
$$\int_0^r e^{-x} \sin(x)\,\mathrm dx$$
\end{document}

dvips gives the following output:

kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 lmex10
mktexpk: don't know how to create bitmap font for lmex10.
kpathsea: Appending font creation commands to missfont.log.
dvips: Font lmex10 not found,  using cmr10 instead.
</usr/share/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk>
dvips: Checksum mismatch in font lmex10

kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 lmmi8
mktexpk: don't know how to create bitmap font for lmmi8.
dvips: Font lmmi8 not found,  using cmr10 instead.
</usr/share/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk>
dvips: Design size mismatch in font lmmi8
dvips: Checksum mismatch in font lmmi8

kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 rm-lmr8
mktexpk: don't know how to create bitmap font for rm-lmr8.
dvips: Font rm-lmr8 not found,  using cmr10 instead.
</usr/share/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk>
dvips: Design size mismatch in font rm-lmr8
dvips: Checksum mismatch in font rm-lmr8

kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 lmmi10
mktexpk: don't know how to create bitmap font for lmmi10.
dvips: Font lmmi10 not found,  using cmr10 instead.
</usr/share/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk>
dvips: Checksum mismatch in font lmmi10

kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 lmsy8
mktexpk: don't know how to create bitmap font for lmsy8.
dvips: Font lmsy8 not found,  using cmr10 instead.
</usr/share/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk>
dvips: Design size mismatch in font lmsy8
dvips: Checksum mismatch in font lmsy8

kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 rm-lmr10
mktexpk: don't know how to create bitmap font for rm-lmr10.
dvips: Font rm-lmr10 not found,  using cmr10 instead.
</usr/share/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk>
dvips: Checksum mismatch in font rm-lmr10
</usr/share/texmf/dvips/base/tex.pro>. [1]

Also, a file named missfont.log is created and contains the following:

mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 lmex10
mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 lmmi8
mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 rm-lmr8
mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 lmmi10
mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 lmsy8
mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 rm-lmr10

I used lmodern several times in the past and it worked correctly. Maybe some update lead to this...

Can anyone confirm this problem or give some hints, how to solve this problem? I tried reinstalling all texlive packages, updmap, fmtutil...

Thanks for help!
Michael

EDIT:
Reinstalling all texlive packages didn't help. But uninstalling them, deleting all files in /usr/share/texmf* and reinstalling them did help. I don't know why, but the problem is solved. Sorry for the inconvenience.

Last edited by Bevan (2010-02-20 23:51:43)

maleadt

Member

Registered: 2010-01-05

Posts: 12

Re: [solved] texlive doesn't work correctly, when lmodern is used

Just to confirm what Bevan posted as solution: erasing those files did fix the latex compilation. It did even more: Gummi (and thus python-poppler, using libpoppler) had been refusing to render correct PDF's, all text had been missing (other PDF viewers, even poppler-based, worked correctly). After erasing those texmf folders, python-poppler now renders PDF's correctly again (although I have no idea how both are related ).

hennes

Member

Registered: 2008-03-31

Posts: 50

Re: [solved] texlive doesn't work correctly, when lmodern is used

Thank you so much! I would never have thought of this solution!!

Cdh

Member

Registered: 2009-02-03

Posts: 1,098

Re: [solved] texlive doesn't work correctly, when lmodern is used

Does anyone know what caused this? I have a similar problem and am uninstalling texlive* at the moment. I mean, some latex tools work partly, some don't find fonts etc. What's the underlying problem here?

edit: Confirmed, that it works now.

Last edited by Cdh (2010-11-15 17:26:54)

---

฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz

ngoonee

Forum Fellow

From: Between Thailand and Singapore

Registered: 2009-03-17

Posts: 7,358

Re: [solved] texlive doesn't work correctly, when lmodern is used

Similar problem here, I also had to clear ~/.texlive besides the steps above.

I believe the issue to be caused by a large texlive update last year and some old configs hanging around (in the various texmf-var).

---

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

menta

Member

From: Hungary

Registered: 2010-07-01

Posts: 5

Re: [solved] texlive doesn't work correctly, when lmodern is used

The way some TeX-related font packages use updmap-sys to update TeX's font database (/etc/texmf/web2c/updmap.cfg) may cause this problem. For me, minionpro started to give similar 'missfont' errors when I upgraded texlive-latexextra.

I don't know the right/best way to handle TeX fonts and use updmap-sys in install files, however installing *.maps files into the /var/lib/texmf/arch/installedpkgs/ directory seems to be a more robust solution than calling updmap-sys with '--enable Map' or '--enable MixedMap' options. Adapting the code used in the build files of texlive-latexextra for minionpro solved the problem for me.

The steps I did:

1. Create *.maps file (minionpro.maps).

2. Modify  the PKGBUILD (modified minionpro PKGBUILD):

   • Add '$pkgname.maps' to the 'source' variable.

   • Add these lines to the top of the build() function:

       install -m755 -d $pkgdir/var/lib/texmf/arch/installedpkgs
       install -m644 $pkgname.maps $pkgdir/var/lib/texmf/arch/installedpkgs/

   • Update the 'md5sums' variable.

3. Modify  the install file to use the *.maps file when updating TeX's font database (modified minionpro.install).

I hope this helps to solve problems related to other TeX fonts as well.