Description of problem: pdflatex fails on the attached beamer source. Version-Release number of selected component (if applicable): texlive-2007-25.fc9.x86_64 How reproducible: Always. Steps to Reproduce: 1. pdflatex talk.tex 2. 3. Actual results: Build fails with error: !pdfTeX error: pdflatex (file /usr/local/share/texmf/tex/latex/beamer/base/art/ beamericonarticle.20.pdf): xpdf: reading PDF image failed ==> Fatal error occurred, no output PDF file produced! Expected results: Normal termination, PDF produced. Additional info: This works with tetex. It builds with TeXLive using latex, dvips, and ps2pdf, but some beamer features are sacrificed that way.
Created attachment 298580 [details] LaTeX file that fails to build with pdflatex.
It works for me. It seems like either beamer instalation or /usr/local/share/texmf/tex/latex/beamer/base/art/ beamericonarticle.20.pdf is damaged, could you please attach the file here?
Ah, got it. I didn't realize it from the first look. It seems like you don't use the original TEXMF tree which is in /usr/share/texmf, your tree is in /usr/local/ ...
I also experienced the same issue but I cannot reproduce it and I don't remember which document it was...
$ diff `locate beamericonarticle.20.pdf` produces no output, so the two files are identical. Something else is going on. (In reply to comment #3) > Ah, got it. I didn't realize it from the first look. It seems like you don't use > the original TEXMF tree which is in /usr/share/texmf, your tree is in > /usr/local/ ... That's because of bug #437375. The packages I have in the /usr/local tree are the most recent beamer, an old foiltex, and a style called mathprog that customizes LaTeX for a journal I write for. Only beamer is relevant here. I thought it had failed for me without the /usr/local tree before, but now it doesn't. It does complain a lot about missing font files, though: pdfTeX warning: pdflatex (file /var/lib/texmf/fonts/map/pdftex/updmap/pdftex.ma p): ambiguous entry for `tosl7': font file present but not included, will be tr eated as font file not present
After updating to texlive-latex-2007-29.fc8.x86_64 and related packages, I can no longer reproduce this problem. Whatever you did, thanks! The font messages still occur, but I'll open a separate bug for those.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.