Bug 745765 - I can't find the format file `pdflatex.fmt'
Summary: I can't find the format file `pdflatex.fmt'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-13 10:43 UTC by David Barton
Modified: 2015-03-05 01:21 UTC (History)
15 users (show)

Fixed In Version:
Clone Of: 578426
Environment:
Last Closed: 2013-08-01 09:08:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Barton 2011-10-13 10:43:34 UTC
This has just hammered me today after the recent update to texlive 2010. Is there any workaround other than reinstalling texlive as that's quite painful!


+++ This bug was initially created as a clone of Bug #578426 +++

Description of problem:
I can't compile tex files.

Version-Release number of selected component (if applicable):
rpm -q texlive
texlive-2009-3.20100329.fc11.x86_64


Steps to Reproduce:
1. only do pdflatex file.tex

Actual results:

pdflatex document.tex
This is pdfTeX, Version 3.1415926-1.40.10 (Web2C 2009)

kpathsea: Running mktexfmt pdflatex.fmt
I can't find the format file `pdflatex.fmt'!


Additional info:


Some error with root, and after doing rm ~/.texlive*.

[toky@localhost rapport]$ ldd `which pdflatex`
	linux-vdso.so.1 =>  (0x00007fffbffa9000)
	libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x0000003655000000)
	libz.so.1 => /lib64/libz.so.1 (0x00000035f9e00000)
	libpoppler.so.4 => /usr/lib64/libpoppler.so.4 (0x0000003b88200000)
	libkpathsea.so.5 => /usr/lib64/libkpathsea.so.5 (0x0000003b5d400000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003603e00000)
	libm.so.6 => /lib64/libm.so.6 (0x00000035f9200000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003600600000)
	libc.so.6 => /lib64/libc.so.6 (0x00000035f8e00000)
	libjpeg.so.62 => /usr/lib64/libjpeg.so.62 (0x0000003608200000)
	libfreetype.so.6 => /usr/lib64/freetype-freeworld/libfreetype.so.6 (0x0000003b99000000)
	libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x0000003b99400000)
	libopenjpeg.so.2 => /usr/lib64/libopenjpeg.so.2 (0x00000031fa800000)
	/lib64/ld-linux-x86-64.so.2 (0x00000035f8a00000)
	libexpat.so.1 => /lib64/libexpat.so.1 (0x00000035fbe00000)

--- Additional comment from jnovy on 2010-03-31 10:14:59 EDT ---

This is likely caused by the texlive-kpathsea update which wipes out essential configuration files. It is because critical config files were not declared as %config(noreplace) in the old package version .

The current package correctly declares the files as %config. So from now on it won't happen. To make your TeX Live installation functional again, please do the following:

# rpm -qa | grep texlive | xargs rpm -e
# yum install texlive

This will place TeX Live back on track.

--- Additional comment from mefoster on 2010-04-01 06:52:43 EDT ---

Note that the above steps also remove the texlive-release package, so you first need to reinstall the appropriate one from http://jnovy.fedorapeople.org/texlive/ before doing the second step.

--- Additional comment from jnovy on 2010-04-01 07:29:40 EDT ---

Yes, forgot the middle step. Thanks for noticing. This is what is needed to be done (for Fedora 11):

# rpm -qa | grep texlive | xargs rpm -e
# rpm -i http://jnovy.fedorapeople.org/texlive/texlive-f11-release-2009-0.3.fc12.noarch.rpm
# yum install texlive

--- Additional comment from bodman on 2010-04-01 18:00:42 EDT ---

it worked, thank a lot :)

--- Additional comment from mefoster on 2010-04-21 05:20:29 EDT ---

This symptom happened again with the most recent update (to texlive-2010-3.20100420) ... I hope that it isn't going to happen every time there's a new version :(

--- Additional comment from a.j.delaney.uk on 2010-12-21 07:12:26 EST ---

I've had this happen again today.  Like Mary Ellen above, I'd appreciate if this didn't happen every update.  There are two similar and long standing bugs which appear (from my un-expert point of view) to report the same issue.

* https://bugzilla.redhat.com/show_bug.cgi?id=590043
* https://bugzilla.redhat.com/show_bug.cgi?id=447062

I'm pulling my TeX Live pacakges from
http://jnovy.fedorapeople.org/texlive/packages.fc14/

--- Additional comment from fedora-bugs on 2010-12-21 19:16:00 EST ---

Hm. I hit this issue, too, after a LaTeX update with the repository http://jnovy.fedorapeople.org/texlive/packages.fc14/ enabled.

Neither a "sudo fmtutil-sys --all" nor a "sudo texhash" helped. "locate pdflatex.fmt" doesn't find anything.

13.20101217.fc14 is my version of texlive.

How can I reopen this bugreport?

--- Additional comment from vonbrand.cl on 2011-06-22 10:46:11 EDT ---

Happened again with today's update to texlive...

--- Additional comment from daw-redhatbugzilla.berkeley.edu on 2011-07-01 19:41:58 EDT ---

Happened to me too.  This should be re-opened.

Looks like my last yum updates of texlive-related packages were Jun 24 and Jun 26.  None of the following helped (run as root): "texhash", "fmtutil-sys --all", "updmap", "mktexlsr", "fmtutil --all", "fmtutil-sys --byfmt pdflatex".

What can I do to help troubleshoot, to ensure this doesn't keep happening in the future?  Given how many times it has happened in the past, I suspect some systematic issue.

Comment 1 Hin-Tak Leung 2012-06-07 15:25:04 UTC
Problem had come back for texlive 2012 (fedora 17).

# rpm -q texlive-release
texlive-release-2012-0.1.20120510_r26283.fc17.noarch

rpm -qf /usr/share/texlive/texmf/web2c/fmtutil.cnf
texlive-kpathsea-svn26056-1.noarch

The solution is to uncomment the few lines below pdflatex in /usr/share/texlive/texmf/web2c/fmtutil.cnf, then run fmtutil-sys --all.

Strangely enough my previous fmtutil.cnf (from texlive 2011) seems to have those lines uncommented, as is apparent from the leafover fmtutil.cnf.rpmsave .

Comment 2 JM 2012-07-02 15:47:14 UTC
Yep, same here for Fedora 17. Comment #1 fixed the problem.

Comment 3 Andrew McNabb 2012-07-03 20:29:39 UTC
I'm experiencing this in Fedora 17, too, and uncommenting the lines and running fmtutil-sys --all seems to have worked around the problem for now.

Comment 4 Germán Racca 2012-07-09 19:49:46 UTC
I didn't see this bug before, but I did "yum reinstall tex-*" and now I am able to compile latex files.

Comment 5 Tadej Janež 2012-10-15 15:36:45 UTC
The same problem occurred when I upgraded from F16 with TexLive 2011 to F17 with TexLive 2012.

The fix suggested in Comment #3 didn't work for me. Only after I run "yum reinstall tex*", as suggested in Comment #4, the problem was fixed.

Comment 6 Jindrich Novy 2013-01-30 19:43:22 UTC
Could you please try to remove all your ~/.texlive-* files and try to compile your sources again?

Comment 7 Tadej Janež 2013-02-13 10:11:55 UTC
(In reply to comment #6)
> Could you please try to remove all your ~/.texlive-* files and try to
> compile your sources again?

Hmm, I'm afraid I won't be able to help.

TexLive 2012 works fine for me after performing the procedure described in comment #5. And I don't have the time to perform the same procedure that triggered the bug again (create a F-16 with TexLive 2011 and upgrade to F17 with TexLive 2012).

Comment 8 Tobias Mueller 2013-05-05 23:58:18 UTC
I think this can be closed. With TexLive now being in Fedora proper, this didn't happen to me after the upgrade.

Comment 10 Fedora End Of Life 2013-07-04 02:41:00 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2013-08-01 09:09:03 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.