Dvips fails in texlive 2022, texlive 2023 and MacTeX

Jim Diamond jim at jdvb.ca
Sat Jul 22 16:41:06 CEST 2023


Hi Florian,

FWIW, here is what I get on Slackware64 15.0:

$ latex sample2e
This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023) (preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(/usr/local/texlive/2023/texmf-dist/tex/latex/base/sample2e.tex
LaTeX2e <2023-06-01> patch level 1
L3 programming layer <2023-06-30>
(/usr/local/texlive/2023/texmf-dist/tex/latex/base/article.cls
Document Class: article 2023/05/17 v1.4n Standard LaTeX document class
(/usr/local/texlive/2023/texmf-dist/tex/latex/base/size10.clo))
(/usr/local/texlive/2023/texmf-dist/tex/latex/l3backend/l3backend-dvips.def)
No file sample2e.aux.
(/usr/local/texlive/2023/texmf-dist/tex/latex/base/omscmr.fd) [1] [2] [3]
(./sample2e.aux) )
Output written on sample2e.dvi (3 pages, 7576 bytes).
Transcript written on sample2e.log.
$ dvips sample2e     
This is dvips(k) 2023.1 (TeX Live 2023)  Copyright 2023 Radical Eye Software (www.radicaleye.com)
' TeX output 2023.07.22:1137' -> sample2e.ps
</usr/local/texlive/2023/texmf-dist/dvips/base/tex.pro>
</usr/local/texlive/2023/texmf-dist/dvips/l3backend/l3backend-dvips.pro>
</usr/local/texlive/2023/texmf-dist/fonts/enc/dvips/cm-super/cm-super-ts1.enc>
</usr/local/texlive/2023/texmf-dist/dvips/base/texps.pro>
</usr/local/texlive/2023/texmf-dist/dvips/base/special.pro>. 
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy7.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi7.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi10.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmti10.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/cm-super/sfrm1000.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmr7.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx12.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb>
</usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb>
[1] [2] [3] 
$

You want to try with my sample2e.dvi file, to try to bisect the error?  It
is attached.

Good luck tracking this down.

                                Jim

On Sat, Jul 22, 2023 at 15:24 (+0200), Florian Colbatzky wrote:

> Yes, the output of which latex and which dvips refers to the same
> directories in MacTeX as well as TeXLife on Debian.
> If I use a terminal and use "dvips sample2e", I get the message "buffer
> overflow detected - terminated" on Debian and "zsh: trace trap  dvips
> sample2e.dvi" on the Mac.

> Am Sa., 22. Juli 2023 um 14:49 Uhr schrieb Zdenek Wagner <
> zdenek.wagner at gmail.com>:

>> I have tried test.dvi with TL 2022 and TL 2023 and both work:

>> $ dvips test.dvi
>> This is dvips(k) 2022.1 (TeX Live 2022)  Copyright 2022 Radical Eye
>> Software (www.radicaleye.com)
>> ' TeX output 2023.07.22:1425' -> test.ps
>> </usr/local/texlive/2022/texmf-dist/dvips/base/tex.pro>
>> </usr/local/texlive/2022/texmf-dist/dvips/l3backend/l3backend-dvips.pro>

>> </usr/local/texlive/2022/texmf-dist/fonts/enc/dvips/cm-super/cm-super-t1.enc>
>> </usr/local/texlive/2022/texmf-dist/dvips/base/texps.pro>
>> </usr/local/texlive/2022/texmf-dist/dvips/base/special.pro>.

>> </usr/local/texlive/2022/texmf-dist/fonts/type1/public/cm-super/sfrm1200.pfb>
>> [1]



>> $ dvips test.dvi
>> This is dvips(k) 2023.1 (TeX Live 2023)  Copyright 2023 Radical Eye
>> Software (www.radicaleye.com)
>> ' TeX output 2023.07.22:1425' -> test.ps
>> </usr/local/texlive/2023/texmf-dist/dvips/base/tex.pro>
>> </usr/local/texlive/2023/texmf-dist/dvips/l3backend/l3backend-dvips.pro>

>> </usr/local/texlive/2023/texmf-dist/fonts/enc/dvips/cm-super/cm-super-t1.enc>
>> </usr/local/texlive/2023/texmf-dist/dvips/base/texps.pro>
>> </usr/local/texlive/2023/texmf-dist/dvips/base/special.pro>.

>> </usr/local/texlive/2023/texmf-dist/fonts/type1/public/cm-super/sfrm1200.pfb>
>> [1]


>> You must have somethiong wrong in your setup. Does which latex and
>> which dvips find the executables in the same path?

>> Zdeněk Wagner
>> https://www.zdenek-wagner.eu/

>> so 22. 7. 2023 v 14:27 odesílatel Florian Colbatzky
>> <colbatzkyfa at gmail.com> napsal:

>>> Howdy,
>>> certainly. Even a simple .tex file as the one attached is properly
>> processed by latex, but then dvips fails with the error already presented.
>>> Thanks.
>>> Florian

>>> Am Sa., 22. Juli 2023 um 13:25 Uhr schrieb Herbert Schulz <
>> herbs2 at mac.com>:



>>>> > On Jul 22, 2023, at 5:05 AM, Florian Colbatzky <colbatzkyfa at gmail.com>
>> wrote:
>>>> >
>>>> > Hello, and thank you for the first responses.
>>>> >
>>>> > Here is some more information:
>>>> > - both Linux (Debian and Kali) installations of TexLive have been
>> done by using either apt install or just by using the Synaptic package
>> manager. On my Mac, I have used the latest MacTeX and regularly updated it
>> with the TeX Live Utility.
>>>> > - the .tex files process without errors using pdflatex
>>>> > - I call dvips either out of the editor like Kile in Linux or
>> TeXStudio on the Mac; I have also tried "dvips name_of_dvifile" in a
>> terminal after changing into the directory with the .dvi file
>>>> > - attached is a text file created in the MacTeX installation with the
>> command "dvips -d -1 name_of_dvifile.dvi > dvips_test_a.txt 2>&1"; a .ps
>> file was not created
>>>> > - the error message in the Linux distributions is:
>>>> > Prozess gestartet: dvips -o "Liste_fuer_CuP".ps "Liste_fuer_CuP".dvi
>>>> > *** buffer overflow detected ***: terminated
>>>> > Kommando abgestürzt: dvips -o "Liste_fuer_CuP".ps "Liste_fuer_CuP".dvi
>>>> > Prozess endete mit Fehler(n)
>>>> >
>>>> > Thanks for any help!
>>>> > Kindest regards,
>>>> > Florian
>>>> >
>>>> >
>>>> > Am Fr., 21. Juli 2023 um 08:42 Uhr schrieb Alois Steindl <
>> Alois.Steindl at tuwien.ac.at>:
>>>> > Hello,
>>>> > you need to provide much more informations about the problem: what
>> happens, when you call dvips? Doesn't it run at all, do you get any error
>> messages from it? Dvips can be called with a debug option, what does it say?
>>>> > Are you sure, that the right dvips is called? How do you call it?
>>>> > Good luck
>>>> > Alois
>>>> >
>>>> > ------ Originalnachricht------
>>>> > Von: Florian Colbatzky
>>>> > Datum: Do., 20. Juli 2023 23:30
>>>> > An: tex-live at tug.org;
>>>> > Cc:
>>>> > Betreff:Dvips fails in texlive 2022, texlive 2023 and MacTeX
>>>> >
>>>> > Dear texlive list members,
>>>> >
>>>> > Just per chance (texlive system check with Kile in one Linux
>> distribution) I have realised that drips does not work anymore, but
>> crashes. I have then checked it in two other Linux distributions and in
>> MacTeX with the same result. I have used different tex (transforming them
>> via LaTeX) and dvi files. Dvipdf works well. The system check of Kile does
>> not complain about other failures .
>>>> >
>>>> > On the Internet, I have not found any information for this problem.
>>>> >
>>>> > Thus, I have decided to make you aware of it. Maybe you even know the
>> reason.
>>>> >
>>>> > With kind regards,
>>>> > Florian Colbatzky
>>>> >
>>>> >
>>>> > --
>>>> > Dr. Florian Colbatzky
>>>> > Matthias-Erzberger-Str. 7/2
>>>> > 88400 Biberach / Riss
>>>> > Germany
>>>> > Tel.: +49 (7357) 91033
>>>> > Fax: +49 (7357) 91035
>>>> > Mail: colbatzkyfa at gmail.com
>>>> >
>>>> > --
>>>> > Dr. Florian Colbatzky
>>>> > Matthias-Erzberger-Str. 7/2
>>>> > 88400 Biberach / Riss
>>>> > Germany
>>>> > Tel.: +49 (7357) 91033
>>>> > Fax: +49 (7357) 91035
>>>> > Mail: colbatzkyfa at gmail.com
>>>> > <dvips-test_a.txt>

>>>> Howdy,

>>>> I have a simple file, Fig2.tex, that includes an eps graphic,
>> stupid.eps. Compiling with `latex Fig2.tex` I get Fig2.dvi. Then

>>>>  % dvips -o "Fig2".ps "Fig2".dvi
>>>> This is dvips(k) 2023.1 (TeX Live 2023)  Copyright 2023 Radical Eye
>> Software (www.radicaleye.com)
>>>> ' TeX output 2023.07.22:0619' -> Fig2.ps
>>>> </usr/local/texlive/2023/texmf-dist/dvips/base/tex.pro>
>>>> </usr/local/texlive/2023/texmf-dist/dvips/l3backend/l3backend-dvips.pro

>>>> </usr/local/texlive/2023/texmf-dist/fonts/enc/dvips/base/8r.enc>
>>>> </usr/local/texlive/2023/texmf-dist/dvips/base/texps.pro>
>>>> </usr/local/texlive/2023/texmf-dist/dvips/base/special.pro>.
>> </usr/local/texlive/texmf-local/fonts/type1/bh/lucida/lbms.pfb>
>>>> </usr/local/texlive/texmf-local/fonts/type1/bh/lucida/lbr.pfb>[1
>>>> <./figs/stupid.eps>]

>>>> and there is no problem producing Fig2.ps.

>>>> Could you please provide a .tex file that gives rise to your problem.

>>>> Good Luck,

>>>> Herb Schulz
>>>> herbs2 at mac.com




>>> --
>>> Dr. Florian Colbatzky
>>> Matthias-Erzberger-Str. 7/2
>>> 88400 Biberach / Riss
>>> Germany
>>> Tel.: +49 (7357) 91033
>>> Fax: +49 (7357) 91035
>>> Mail: colbatzkyfa at gmail.com



> -- 
> Dr. Florian Colbatzky
> Matthias-Erzberger-Str. 7/2
> 88400 Biberach / Riss
> Germany
> Tel.: +49 (7357) 91033
> Fax: +49 (7357) 91035
> Mail: colbatzkyfa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sample2e.dvi
Type: application/x-dvi
Size: 7576 bytes
Desc: not available
URL: <https://tug.org/pipermail/tex-live/attachments/20230722/29edc299/attachment.dvi>


More information about the tex-live mailing list.