Since Tumbleweed 20172025, texlive appears to be broken.
When will this problem get resolved?
Depends on when a bug report (i.e. YOUR bug report on this issue) will be dealt with.
(I hope you get the hint.)
AK
P.S. https://bugzilla.opensuse.org/
You can use the same login credentials you use for this forum.
Not the new updates, but the software in my machine got corrupted somehow.
Sorry for the misplaced posting.
I think we can close this thread.
abonfi
June 28, 2017, 1:27pm
4
Same problem on two different machines running openSUSE Tumbleweed following the latest update.
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/TeX Live for SUSE Linux) (preloaded format=latex)
fmtutil --all
won’t fix it.
What if I do NOT want to re-install?
I suggest that you reopen the existing bug report:Bug 1046277
Click on the link. You should be able to login with the same credentials that you use for opensuse forums. And you might already be logged in.
Look for the edit box “Additional comments”. Put your comment there. Mention that you tried “fmtutil --all”. Just below that edit box, is a status line. Change that from “RESOLVED” to “RE-OPEN”. Then submit your changes.
It seems to be working for me. And I did not do a reinstall. Checking that “latex.fmt” file, I see that it has a date of Jun 26, which is when I installed that large update which included texlive.
Apparently there is some problem with updating format files that is affecting you but not affecting me.
abonfi
June 28, 2017, 6:00pm
6
ls -l /var/lib/texmf/web2c/pdftex/latex.fmt
whereas texlive has been updated on june 28th
I see that you have reopened the bug report. I suggest you add the “ls” output to the report. It gives a point of information on what has gone wrong.
Hi, I have the same problem (the link to bug don’t works for me). If I run the command “fmtutil-sys --all” I get:
(/usr/share/texmf/tex/generic/babel/hyphen.cfgdehypht-x' 2017-03-31 (W L))) (/usr/share/texmf/tex/generic/dehyph-exptl/dehyphn-x-2017-03-31.tex dehyph-exptl: using an 8-bit TeX engine. (/usr/share/texmf/tex/generic/dehyph-exptl/dehyphn-x-2017-03-31.pat German Hyphenation Patterns (Reformed Orthography, 2006) dehyphn-x’ 2017-03-31
(Press Enter to retry, or Control-D to exit)
! ==> Fatal error occurred, no output PDF file produced!xetex -ini -jobname=xetex -progname=xetex -etex xetex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running pdftex -ini -jobname=pdftex -progname=pdftex -translate-file=cp227.tcx *pdfetex.ini </dev/null’ return status 1pdftex -ini -jobname=latex -progname=latex -translate-file=cp227.tcx *latex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running pdftex -ini -jobname=mllatex -progname=mllatex -translate-file=cp227.tcx -mltex *mllatex.ini </dev/null’ return status 1pdftex -ini -jobname=pdfjadetex -progname=pdfjadetex -translate-file=cp227.tcx *pdfjadetex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running pdftex -ini -jobname=pdflatex -progname=pdflatex -translate-file=cp227.tcx *pdflatex.ini </dev/null’ return status 1xetex -ini -jobname=xelatex -progname=xelatex -etex xelatex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running pdftex -ini -jobname=pdfetex -progname=pdfetex -translate-file=cp227.tcx *pdfetex.ini </dev/null’ return status 1pdftex -ini -jobname=etex -progname=etex -translate-file=cp227.tcx *etex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running pdftex -ini -jobname=jadetex -progname=jadetex -translate-file=cp227.tcx *jadetex.ini </dev/null’ return status 1pdftex -ini -jobname=xmltex -progname=xmltex -translate-file=cp227.tcx *xmltex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running pdftex -ini -jobname=pdfxmltex -progname=pdfxmltex -translate-file=cp227.tcx *pdfxmltex.ini </dev/null’ return status 1
Some idea?
I have not been able to access bug reports since yesterday afternoon. I think something broke. Hopefully it will be available again soon.