On 2019-05-25, Kornel Benko wrote:
> Am Samstag, 25. Mai 2019, 10:09:18 CEST schrieb Guenter Milde:
>> On 2019-05-24, Kornel Benko wrote:
>> > Am Freitag, 24. Mai 2019, 18:07:13 CEST schrieb Guenter Milde:

> ...

>> > This is the same warning as for export/doc/fr/Customization_pdf5_systemF.

>> ... and probably most/all of the failing (pdf5|dvi3)_systemF tests.

>> > We use deprecated (since 2008!) interface.

>> Not directly. Could you create a minimal example to see which package is
>> defining this macro (deprecated by KOMA, not necessarily by the full LaTeX
>> community)? We may then consider to use an alternative or to suppress the
>> warning with "scrhack".


> I tried, and it seems that the suspected warning is _not_ the reason
> for lualatex to fail.

> The attached fails, but there is no error sign in the latex log.

Thanks for investigating.

> Exporting to tex and calling lualatex manually, the compilation stops with:
>       (/usr9/local/texlive/2019/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
>       [Loading MPS to PDF converter (version 2006.09.02).]
>       ) (/usr9/local/texlive/2019/texmf-dist/tex/latex/hyperref/nameref.sty
>       
> (/usr9/local/texlive/2019/texmf-dist/tex/generic/oberdiek/gettitlestring.sty))
>       (/usr9/local/texlive/2019/texmf-dist/tex/latex/oberdiek/bookmark.sty
>       (/usr9/local/texlive/2019/texmf-dist/tex/latex/oberdiek/bkm-pdftex.def))
>       
> [1{/usr9/local/texlive/2019/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]
>       warning  (node filter): error: 
> ...19/texmf-dist/tex/latex/polyglossia/polygloss
>       ia-frpt.lua:166: attempt to call a nil value (upvalue 'remove_node')

>       .
>       \newpage ...k \@nobreakfalse \everypar {}\fi \par 
>                                                   \ifdim \prevdepth >\z@ 
> \vs...

>       l.64 \end{document}

Maybe you can also find out which part of the document triggers the error.
(Unfortunately, the error message does not help much as the error seems to
manifest only after the complete document is read.)

If it is the user preamble code, we may try to make it more robust.

In case it is some package, contact the package author.

Otherwise, it may be best to report this to the luatex developers.

Günter

Reply via email to