Error: I can't find the format file pdflatex.fmt
For no particular reason that I could identify, I was faced with the impossibility to compile any latex document and invariably got this error message each time I tried :
LaTeX: problems after [0] pages
kpathsea: Running mktexfmt pdflatex.fmt
tcfmgr: config file `tcfmgr.map' (usually in $TEXMFMAIN/texconfig) not found.
I can't find the format file `pdflatex.fmt'!
pdftex
add a comment |
For no particular reason that I could identify, I was faced with the impossibility to compile any latex document and invariably got this error message each time I tried :
LaTeX: problems after [0] pages
kpathsea: Running mktexfmt pdflatex.fmt
tcfmgr: config file `tcfmgr.map' (usually in $TEXMFMAIN/texconfig) not found.
I can't find the format file `pdflatex.fmt'!
pdftex
For me I simply had to copy the .fmt file into the directory the PHP file was calling it from. It worked fine from a terminal but gave the error when running via PHP.
– Alan
Feb 17 '15 at 15:53
add a comment |
For no particular reason that I could identify, I was faced with the impossibility to compile any latex document and invariably got this error message each time I tried :
LaTeX: problems after [0] pages
kpathsea: Running mktexfmt pdflatex.fmt
tcfmgr: config file `tcfmgr.map' (usually in $TEXMFMAIN/texconfig) not found.
I can't find the format file `pdflatex.fmt'!
pdftex
For no particular reason that I could identify, I was faced with the impossibility to compile any latex document and invariably got this error message each time I tried :
LaTeX: problems after [0] pages
kpathsea: Running mktexfmt pdflatex.fmt
tcfmgr: config file `tcfmgr.map' (usually in $TEXMFMAIN/texconfig) not found.
I can't find the format file `pdflatex.fmt'!
pdftex
pdftex
edited Oct 6 '12 at 18:20
Joseph Wright♦
203k22559885
203k22559885
asked Jul 27 '12 at 11:49
Alfred M.Alfred M.
1,27411553
1,27411553
For me I simply had to copy the .fmt file into the directory the PHP file was calling it from. It worked fine from a terminal but gave the error when running via PHP.
– Alan
Feb 17 '15 at 15:53
add a comment |
For me I simply had to copy the .fmt file into the directory the PHP file was calling it from. It worked fine from a terminal but gave the error when running via PHP.
– Alan
Feb 17 '15 at 15:53
For me I simply had to copy the .fmt file into the directory the PHP file was calling it from. It worked fine from a terminal but gave the error when running via PHP.
– Alan
Feb 17 '15 at 15:53
For me I simply had to copy the .fmt file into the directory the PHP file was calling it from. It worked fine from a terminal but gave the error when running via PHP.
– Alan
Feb 17 '15 at 15:53
add a comment |
5 Answers
5
active
oldest
votes
I thought I would post this here because it gave me some cold sweats as I could not make any sense of the error message and have only two months remaining to write my thesis.
In a terminal, just type
sudo texconfig rehash
which should give
mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVE...
mktexlsr: Updating /var/lib/texmf/ls-R...
mktexlsr: Done.
This solution was found on this website.
3
This answer led to another question. It is easier and more conventional to simply usesudo texhash.
– Serge Stroobandt
Jun 20 '13 at 9:31
2
Both rehash and texhash produce an analogous output, but I am still returned the same errore message.
– Delio
Sep 25 '14 at 13:23
add a comment |
I had this problem and none of the sites I visited helped. This is for linux. I was installing on a semi-incomplete backed-up image of a previous computer. My problem turned out to be the pre-existing config files in /etc/texmf/updmap.d
This is what I did:
Remove all tex packages:
sudo apt-get remove texlive*PURGE all tex packages:
sudo apt-get purge texlive*Delete everything in /etc/texmf/updmap.d
Re-install desired tex packages:
sudo apt-get install texlive etc
It now seems to work fine.
Phil
add a comment |
I solved the same problem in openSUSE Tumbleweed with re-installing texlive via
zypper remove texlive*
zypper install texlive
This doesn't work if recommended packages are not set to be installed as well.
– ytg
Dec 22 '17 at 15:34
add a comment |
Check whether the file is in your TeX search path.
kpsewhich pdflatex.ini
If the result is empty, then add path to TEXINPUTS, e.g. put into .bash_profile
export TEXINPUTS=.:/opt/tex/cur/texmf-dist/tex/latex/latexconfig/
UPD. If this doesn't help with other paths, it means that your installation is corrupt. To reisntall would be better in that case (I'm doing that at the moment).
add a comment |
If this can be of any help it happened the same to me and I realized that, since the last time I had opened Texmaker, I had installed Anaconda. It turns out that Anaconda had installed a texlive-core package, which was conflicting with my original texlive installation.
I just had to remove the anaconda package through:
conda remove texlive-core
and it worked. None of the previous solutions worked for me for obvious reasons.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f64894%2ferror-i-cant-find-the-format-file-pdflatex-fmt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
I thought I would post this here because it gave me some cold sweats as I could not make any sense of the error message and have only two months remaining to write my thesis.
In a terminal, just type
sudo texconfig rehash
which should give
mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVE...
mktexlsr: Updating /var/lib/texmf/ls-R...
mktexlsr: Done.
This solution was found on this website.
3
This answer led to another question. It is easier and more conventional to simply usesudo texhash.
– Serge Stroobandt
Jun 20 '13 at 9:31
2
Both rehash and texhash produce an analogous output, but I am still returned the same errore message.
– Delio
Sep 25 '14 at 13:23
add a comment |
I thought I would post this here because it gave me some cold sweats as I could not make any sense of the error message and have only two months remaining to write my thesis.
In a terminal, just type
sudo texconfig rehash
which should give
mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVE...
mktexlsr: Updating /var/lib/texmf/ls-R...
mktexlsr: Done.
This solution was found on this website.
3
This answer led to another question. It is easier and more conventional to simply usesudo texhash.
– Serge Stroobandt
Jun 20 '13 at 9:31
2
Both rehash and texhash produce an analogous output, but I am still returned the same errore message.
– Delio
Sep 25 '14 at 13:23
add a comment |
I thought I would post this here because it gave me some cold sweats as I could not make any sense of the error message and have only two months remaining to write my thesis.
In a terminal, just type
sudo texconfig rehash
which should give
mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVE...
mktexlsr: Updating /var/lib/texmf/ls-R...
mktexlsr: Done.
This solution was found on this website.
I thought I would post this here because it gave me some cold sweats as I could not make any sense of the error message and have only two months remaining to write my thesis.
In a terminal, just type
sudo texconfig rehash
which should give
mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVE...
mktexlsr: Updating /var/lib/texmf/ls-R...
mktexlsr: Done.
This solution was found on this website.
edited 12 mins ago
darthbith
5,46831949
5,46831949
answered Jul 27 '12 at 11:49
Alfred M.Alfred M.
1,27411553
1,27411553
3
This answer led to another question. It is easier and more conventional to simply usesudo texhash.
– Serge Stroobandt
Jun 20 '13 at 9:31
2
Both rehash and texhash produce an analogous output, but I am still returned the same errore message.
– Delio
Sep 25 '14 at 13:23
add a comment |
3
This answer led to another question. It is easier and more conventional to simply usesudo texhash.
– Serge Stroobandt
Jun 20 '13 at 9:31
2
Both rehash and texhash produce an analogous output, but I am still returned the same errore message.
– Delio
Sep 25 '14 at 13:23
3
3
This answer led to another question. It is easier and more conventional to simply use
sudo texhash.– Serge Stroobandt
Jun 20 '13 at 9:31
This answer led to another question. It is easier and more conventional to simply use
sudo texhash.– Serge Stroobandt
Jun 20 '13 at 9:31
2
2
Both rehash and texhash produce an analogous output, but I am still returned the same errore message.
– Delio
Sep 25 '14 at 13:23
Both rehash and texhash produce an analogous output, but I am still returned the same errore message.
– Delio
Sep 25 '14 at 13:23
add a comment |
I had this problem and none of the sites I visited helped. This is for linux. I was installing on a semi-incomplete backed-up image of a previous computer. My problem turned out to be the pre-existing config files in /etc/texmf/updmap.d
This is what I did:
Remove all tex packages:
sudo apt-get remove texlive*PURGE all tex packages:
sudo apt-get purge texlive*Delete everything in /etc/texmf/updmap.d
Re-install desired tex packages:
sudo apt-get install texlive etc
It now seems to work fine.
Phil
add a comment |
I had this problem and none of the sites I visited helped. This is for linux. I was installing on a semi-incomplete backed-up image of a previous computer. My problem turned out to be the pre-existing config files in /etc/texmf/updmap.d
This is what I did:
Remove all tex packages:
sudo apt-get remove texlive*PURGE all tex packages:
sudo apt-get purge texlive*Delete everything in /etc/texmf/updmap.d
Re-install desired tex packages:
sudo apt-get install texlive etc
It now seems to work fine.
Phil
add a comment |
I had this problem and none of the sites I visited helped. This is for linux. I was installing on a semi-incomplete backed-up image of a previous computer. My problem turned out to be the pre-existing config files in /etc/texmf/updmap.d
This is what I did:
Remove all tex packages:
sudo apt-get remove texlive*PURGE all tex packages:
sudo apt-get purge texlive*Delete everything in /etc/texmf/updmap.d
Re-install desired tex packages:
sudo apt-get install texlive etc
It now seems to work fine.
Phil
I had this problem and none of the sites I visited helped. This is for linux. I was installing on a semi-incomplete backed-up image of a previous computer. My problem turned out to be the pre-existing config files in /etc/texmf/updmap.d
This is what I did:
Remove all tex packages:
sudo apt-get remove texlive*PURGE all tex packages:
sudo apt-get purge texlive*Delete everything in /etc/texmf/updmap.d
Re-install desired tex packages:
sudo apt-get install texlive etc
It now seems to work fine.
Phil
edited Feb 24 '17 at 8:35
Alfred M.
1,27411553
1,27411553
answered May 2 '16 at 10:33
PhilPhil
211
211
add a comment |
add a comment |
I solved the same problem in openSUSE Tumbleweed with re-installing texlive via
zypper remove texlive*
zypper install texlive
This doesn't work if recommended packages are not set to be installed as well.
– ytg
Dec 22 '17 at 15:34
add a comment |
I solved the same problem in openSUSE Tumbleweed with re-installing texlive via
zypper remove texlive*
zypper install texlive
This doesn't work if recommended packages are not set to be installed as well.
– ytg
Dec 22 '17 at 15:34
add a comment |
I solved the same problem in openSUSE Tumbleweed with re-installing texlive via
zypper remove texlive*
zypper install texlive
I solved the same problem in openSUSE Tumbleweed with re-installing texlive via
zypper remove texlive*
zypper install texlive
edited Jan 21 '17 at 0:12
Zarko
123k865161
123k865161
answered Jan 20 '17 at 23:33
umichumich
11
11
This doesn't work if recommended packages are not set to be installed as well.
– ytg
Dec 22 '17 at 15:34
add a comment |
This doesn't work if recommended packages are not set to be installed as well.
– ytg
Dec 22 '17 at 15:34
This doesn't work if recommended packages are not set to be installed as well.
– ytg
Dec 22 '17 at 15:34
This doesn't work if recommended packages are not set to be installed as well.
– ytg
Dec 22 '17 at 15:34
add a comment |
Check whether the file is in your TeX search path.
kpsewhich pdflatex.ini
If the result is empty, then add path to TEXINPUTS, e.g. put into .bash_profile
export TEXINPUTS=.:/opt/tex/cur/texmf-dist/tex/latex/latexconfig/
UPD. If this doesn't help with other paths, it means that your installation is corrupt. To reisntall would be better in that case (I'm doing that at the moment).
add a comment |
Check whether the file is in your TeX search path.
kpsewhich pdflatex.ini
If the result is empty, then add path to TEXINPUTS, e.g. put into .bash_profile
export TEXINPUTS=.:/opt/tex/cur/texmf-dist/tex/latex/latexconfig/
UPD. If this doesn't help with other paths, it means that your installation is corrupt. To reisntall would be better in that case (I'm doing that at the moment).
add a comment |
Check whether the file is in your TeX search path.
kpsewhich pdflatex.ini
If the result is empty, then add path to TEXINPUTS, e.g. put into .bash_profile
export TEXINPUTS=.:/opt/tex/cur/texmf-dist/tex/latex/latexconfig/
UPD. If this doesn't help with other paths, it means that your installation is corrupt. To reisntall would be better in that case (I'm doing that at the moment).
Check whether the file is in your TeX search path.
kpsewhich pdflatex.ini
If the result is empty, then add path to TEXINPUTS, e.g. put into .bash_profile
export TEXINPUTS=.:/opt/tex/cur/texmf-dist/tex/latex/latexconfig/
UPD. If this doesn't help with other paths, it means that your installation is corrupt. To reisntall would be better in that case (I'm doing that at the moment).
edited Jun 12 '17 at 18:42
answered Jun 12 '17 at 15:37
Yaroslav NikitenkoYaroslav Nikitenko
27927
27927
add a comment |
add a comment |
If this can be of any help it happened the same to me and I realized that, since the last time I had opened Texmaker, I had installed Anaconda. It turns out that Anaconda had installed a texlive-core package, which was conflicting with my original texlive installation.
I just had to remove the anaconda package through:
conda remove texlive-core
and it worked. None of the previous solutions worked for me for obvious reasons.
add a comment |
If this can be of any help it happened the same to me and I realized that, since the last time I had opened Texmaker, I had installed Anaconda. It turns out that Anaconda had installed a texlive-core package, which was conflicting with my original texlive installation.
I just had to remove the anaconda package through:
conda remove texlive-core
and it worked. None of the previous solutions worked for me for obvious reasons.
add a comment |
If this can be of any help it happened the same to me and I realized that, since the last time I had opened Texmaker, I had installed Anaconda. It turns out that Anaconda had installed a texlive-core package, which was conflicting with my original texlive installation.
I just had to remove the anaconda package through:
conda remove texlive-core
and it worked. None of the previous solutions worked for me for obvious reasons.
If this can be of any help it happened the same to me and I realized that, since the last time I had opened Texmaker, I had installed Anaconda. It turns out that Anaconda had installed a texlive-core package, which was conflicting with my original texlive installation.
I just had to remove the anaconda package through:
conda remove texlive-core
and it worked. None of the previous solutions worked for me for obvious reasons.
answered Jul 29 '18 at 17:47
osbornereosbornere
1
1
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f64894%2ferror-i-cant-find-the-format-file-pdflatex-fmt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
For me I simply had to copy the .fmt file into the directory the PHP file was calling it from. It worked fine from a terminal but gave the error when running via PHP.
– Alan
Feb 17 '15 at 15:53