Bugzilla – Bug 1074128
Unable to compile Latex in Tumbleweed 'kpathsea running mktexfmt pdflatex.fmt'
Last modified: 2023-04-24 14:30:35 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Build Identifier: mktexfmt [ERROR]: -user mode but path setup is -sys type, bailing out this happens at every compilation attempt with several different programs and even manual compilation with lualatex texlive scheme base and full and manual texlie have been tested Reproducible: Always Steps to Reproduce: 1.install texlive scheme full https://software.opensuse.org/package/texlive-scheme-full 2. zypper in texstudio select lualatex 3. try to compile anything in texstudio Actual Results: mktexfmt [ERROR]: -user mode but path setup is -sys type, bailing out Expected Results: working latex compilation
Created attachment 754318 [details] screen of error messae
It is even worse if you use texlive-base from the tex rpm group within yast. Or install texlive-base with zypper. It will first result in path errors which you can fix with mktexlsr but after that you also run into the kpathsea error already described. It btw happens with every latex compiler not only lualatex.
Created attachment 754740 [details] error message from fmtutil --all This seems to happen to clean new installation of texlive and also updated or upgraded texlive installations. Attached the error log from fmtutil --all. Looks like it fails for: pdftex/pdftex euptex/euptex xetex/xetex pdftex/mllatex pdftex/eplain pdftex/xmltex pdftex/etex pdftex/pdfetex xetex/xelatex pdftex/pdfxmltex pdftex/pdflatex pdftex/latex pdftex/jadetex pdftex/pdfjadetex
Never seen that ... I guess from log that this due missed hyphen. The only problem is that the hyphen patterns are always recreated during installation of any hyphen package. But this works only if scripts are not disabled or the file system layout is not fully broken. In short words: I can not reproduce this! Show more than log files, show me the file system layout for /etc, etc/texmf, /usr, /usr/share, /usr/share/texmf, and /usr/share/texmf/ for example the output of kpsewhich language.dat kpsewhich language.def kpsewhich language.dat.lua find /usr/share/texmf/ -name language.dat.lua -or \ -name language.def -or \ -name language.dat | xargs ls -gl ls -l /run/texlive/ then we might see what is really going wrong here. Also search in /var/log/zypper.log for executions of the üposttrans scriplets of the packages grep -A3 -E 'zypp::posttrans.*texlive' /var/log/zypper.log
I could reproduce it without any problems in a vm with a fresh Tumbleweed install several times. I changed absolutly nothing in the filesystem. i am at the moment not on suse anymore, due to this bug. Are you not able to reproduce this wihtin a VM? Should not be a problem, as i said it happens regardles of installation method, be it texlive-base via zypper, texlive tree selection in yast2 or the texlive full scheme from the website i mentioned. All of these option ON FRESH UNTOUCHED INSTALLTIONS of Tumbleweed result in the same error. When you use texlive-base via zypper you also have to fix the path error before this error appears. i could send you a vm image with this error if needed.
I have the exact same problem - fresh Tumbleweed install and installing texlive using zypper results in a broken TeX system. If there is anything I can check on my system please let me know. When I have some time tonight or tomorrow I'll check the log files you mentioned and report back.
Hmmm ... please run as root /usr/share/texmf/texconfig/update guess that this should solve the trouble
Created attachment 755143 [details] requested log output
localhost:/usr/share/texmf/texconfig # ./update localhost:/usr/share/texmf/texconfig # sh update did not solve anything in my case. i am on a vm again i will post some logs in few minutes
localhost:/usr/share/texmf/texconfig # kpsewhich language.dat /etc/texmf/tex/generic/config/language.dat localhost:/usr/share/texmf/texconfig # kpsewhich language.def /etc/texmf/tex/generic/config/language.def localhost:/usr/share/texmf/texconfig # kpsewhich language.dat.lua /etc/texmf/tex/generic/config/language.dat.lua localhost:/usr/share/texmf/texconfig # find /usr/share/texmf/ > -name language.dat.lua -or \ > -name language.def -or \ > -name language.dat | xargs ls -gl lrwxrwxrwx 1 root 42 16. Dez 21:23 /usr/share/texmf/tex/generic/config/language.dat -> /etc/texmf/tex/generic/config/language.dat lrwxrwxrwx 1 root 46 16. Dez 21:23 /usr/share/texmf/tex/generic/config/language.dat.lua -> /etc/texmf/tex/generic/config/language.dat.lua lrwxrwxrwx 1 root 42 16. Dez 21:23 /usr/share/texmf/tex/generic/config/language.def -> /etc/texmf/tex/generic/config/language.def localhost:/ # ls -l /run/texlive/ ls: Zugriff auf '/run/texlive/' nicht möglich: Datei oder Verzeichnis nicht gefunden
No, it doesn't. Tried that before, still the same result and error
Created attachment 755145 [details] filesystem layout
(In reply to dude bro from comment #10) > localhost:/usr/share/texmf/texconfig # kpsewhich language.dat > /etc/texmf/tex/generic/config/language.dat > localhost:/usr/share/texmf/texconfig # kpsewhich language.def > /etc/texmf/tex/generic/config/language.def > localhost:/usr/share/texmf/texconfig # kpsewhich language.dat.lua > /etc/texmf/tex/generic/config/language.dat.lua > localhost:/usr/share/texmf/texconfig # find /usr/share/texmf/ > > -name language.dat.lua -or \ > > -name language.def -or \ > > -name language.dat | xargs ls -gl > lrwxrwxrwx 1 root 42 16. Dez 21:23 > /usr/share/texmf/tex/generic/config/language.dat -> > /etc/texmf/tex/generic/config/language.dat > lrwxrwxrwx 1 root 46 16. Dez 21:23 > /usr/share/texmf/tex/generic/config/language.dat.lua -> > /etc/texmf/tex/generic/config/language.dat.lua > lrwxrwxrwx 1 root 42 16. Dez 21:23 > /usr/share/texmf/tex/generic/config/language.def -> > /etc/texmf/tex/generic/config/language.def > > localhost:/ # ls -l /run/texlive/ > > ls: Zugriff auf '/run/texlive/' nicht möglich: Datei oder Verzeichnis nicht > gefunden You have to do this as super user root! Do su mkdir /run/texlive touch /var/run/texlive/run-hyphen touch /var/run/texlive/run-fmtutil.language touch /var/run/texlive/run-fmtutil.refresh /usr/share/texmf/texconfig/update
Working now. Whatever it was exactly should be fixed in future tumbleweeds. Thx for the help. Do you stil need something?
(In reply to dude bro from comment #14) > Working now. > > Whatever it was exactly should be fixed in future tumbleweeds. > > Thx for the help. > > Do you stil need something? The only thing I'd like to know is why the /run/texlive had not exist on your installation ... this temporary directory on the tmpfs /run is created with every texlive packages which triggers a refresh of the formats like hyphen packages. Only a reboot could cause that this temporary directory and its trigger files get lost.
i don't recall rebooting it after the texlive installation. Why would i? If you want i setup a new tumbleweed and post what happens.
This is an autogenerated message for OBS integration: This bug (1074128) was mentioned in https://build.opensuse.org/request/show/562513 Factory / texlive https://build.opensuse.org/request/show/562514 Factory / texlive-filesystem https://build.opensuse.org/request/show/562515 Factory / texlive-specs-a https://build.opensuse.org/request/show/562516 Factory / texlive-specs-b https://build.opensuse.org/request/show/562517 Factory / texlive-specs-c https://build.opensuse.org/request/show/562518 Factory / texlive-specs-d https://build.opensuse.org/request/show/562519 Factory / texlive-specs-e https://build.opensuse.org/request/show/562520 Factory / texlive-specs-f https://build.opensuse.org/request/show/562521 Factory / texlive-specs-g https://build.opensuse.org/request/show/562523 Factory / texlive-specs-h https://build.opensuse.org/request/show/562524 Factory / texlive-specs-i https://build.opensuse.org/request/show/562525 Factory / texlive-specs-j https://build.opensuse.org/request/show/562526 Factory / texlive-specs-k https://build.opensuse.org/request/show/562527 Factory / texlive-specs-l https://build.opensuse.org/request/show/562528 Factory / texlive-specs-m https://build.opensuse.org/request/show/562529 Factory / texlive-specs-n https://build.opensuse.org/request/show/562530 Factory / texlive-specs-o https://build.opensuse.org/request/show/562531 Factory / texlive-specs-p https://build.opensuse.org/request/show/562532 Factory / texlive-specs-q https://build.opensuse.org/request/show/562533 Factory / texlive-specs-r https://build.opensuse.org/request/show/562534 Factory / texlive-specs-s https://build.opensuse.org/request/show/562536 Factory / texlive-specs-t https://build.opensuse.org/request/show/562538 Factory / texlive-specs-u https://build.opensuse.org/request/show/562539 Factory / texlive-specs-v https://build.opensuse.org/request/show/562541 Factory / texlive-specs-w https://build.opensuse.org/request/show/562542 Factory / texlive-specs-x https://build.opensuse.org/request/show/562543 Factory / texlive-specs-y https://build.opensuse.org/request/show/562544 Factory / texlive-specs-z
This is an autogenerated message for OBS integration: This bug (1074128) was mentioned in https://build.opensuse.org/request/show/563596 Factory / texlive-specs-w https://build.opensuse.org/request/show/563597 Factory / texlive-filesystem
fixed