# beamer and: Re: [OS X TeX] TexShop Configuration

Roussanka Loukanova rloukano at stp.lingfil.uu.se
Tue Feb 20 13:10:55 EST 2007

Hi,

On Tue, 20 Feb 2007, S P Suresh wrote:
...

> Thanks for all the help, again. So apart from latexmk looping when it meets
> beamer, and the number of runs with endnotes, there are no issues as of now.

Just in case, because it might be relevant, and you might have missed the
following information about beamer: many problems with beamer files
disappear with the following fix:

in

/usr/local/gwTeX/texmf.texlive/tex/latex/beamer/beamerbaseboxes.sty
/usr/local/texlive/2007/texmf-dist/tex/latex/beamer/beamerbaseboxes.sty

replace the line

\setbox\bmb at colorbox=\hbox{\color{lower.bg}}%

by the line

\setbox\bmb at colorbox=\hbox{{\pgfpicturetrue\pgfsetcolor{lower.bg}}}%

Without this fix, I get various beamer files in loop with pdflatex. And
even after that fix, the command latex does not process beamer files. (I
do not know if this is normal or not: at some point we were supposed to
use only pdflatex with beamer.) For example, if I have a beamer file with
lines

\includegraphics[width=0.6\textwidth]{file.jpg}
or
\includegraphics[width=0.6\textwidth]{file.pdf}
or
\includegraphics[width=0.6\textwidth]{file.png}

the command latex exits with:

! LaTeX Error: Cannot determine size of graphic in picture.png (no BoundingBox).

LaTeX exited abnormally with code 1 at Tue Feb 20 18:56:40

I would appreciate some feedback if this is not supposed to be so, and
any information about it anyway. But most likely, this is a question to
some beamer list.

Roussanka

>
> noticed that the developer of rubber works in a lab with whom we have some
> ties. Maybe I will run into him one of these days. That would be a nice
> coincidence!
>
> Cheers,
> Suresh
>
> S P Suresh
> Chennai Mathematical Institute
> India
>
>
>
> On 20-Feb-07, at 20 Feb,10:11 , Herbert Schulz wrote:
>
>>
>> On Feb 20, 2007, at 9:57 AM, S P Suresh wrote:
>>
>>> Hi Herb,
>>>
>>> ...
>>> (Before the completion of the mail, I got to try it out on a subset of
>>> that same document. It stops after six runs but gives the following
>>> message(s) before quitting:
>>>
>>> Transcript written on tark07.log.
>>> Latexmk: Input bbl file "./tark07.bbl", so turn on bibtex_mode
>>> Latexmk: Failed to find one or more bibliography files in [ref.bib]
>>> Latexmk: Failed to find one or more bib files
>>> Latexmk: File "./tark07.aux" has not changed, so it is valid
>>> Latexmk: File './tark07.ent' changed during run.  I must rerun latex
>>> Latexmk: Absolute maximum runs of latex reached without finding stable
>>> source files
>>>
>>> I don't understand the messages about the bib files. It is always output
>>> at the end. Even when all the bib files are present and it correctly
>>> typesets. But what about the last message?)
>>>
>>>
>>
>> Howdy,
>>
>> Hmmm... I'm also seeing the equivalent of the last two lines in my test
>> file; didn't notice that before---the final results look ok here. The .ent
>> file is something created by the endnote package so I'm not sure why it is
>> driving latexmk crazy. Another bug to report to John Collins.
>>
>> As far as the bibliography problem is concerned, would you copy the
>> contents of the (pdf)latexmk.engine file you are using here. Latexmk tries
>> to use BIBINPUTS to find bib files before bibtex, which uses kpsewhich,
>> does. With most TeX distribution on OS X the BIBINPUTS shell variable isn't
>> set so you can get an error message from latexmk. I fixed'' this in later
>> versions of the engine files by basically setting the BIBINPUTS variable to
>> the path along which kpsewhich searches. This is only a temporary fix and
>> latexmk should really be using kpsewhich to search for the bib file; John
>> message from latexmk is not just the spurious one.
>>
>>> While I am at it, here is another thing that happened with the same paper.
>>> In the early stages, when I hadn't inserted the citations, latexmk would
>>> quit with the following message:
>>>
>>> This is BibTeX, Version 0.99c (Web2C 7.5.6)
>>> The top-level auxiliary file: tark07.aux
>>> The style file: alpha.bst
>>> I found no \citation commands---while reading file tark07.aux
>>> Database file #1: ref.bib
>>> (There was 1 error message)
>>> Latexmk: Did not finish processing file: Bibtex reported an error
>>> Latexmk: Use the -f option to force complete processing.
>>>
>>
>> This looks like bibtex is reporting an error when it find no citations in
>> the .aux file. Latexmk gets this error and quits. You should be able to
>> force latexmk to ignore the error by editing the (xe/pdf)latexmk.engine
>> file and adding the -f option to the command line given there.
>>
>>> I thought BibTeX wouldn't even be called in such cases! This means that I
>>> 	%!TEX_PROGRAM = pdflatexmk
>>> to my documents by default. Have you seen similar behaviour / do you have
>>> any suggestions?
>>>
>>
>> I'll be you get the same error message from bibtex when you process on the
>> command line. The difference is that you ignored it :-).
>>
>>> BTW, just in case you think I am all complaints, let me hasten to add that
>>> first time I saw your mail about it (four / five months ago, maybe) and
>>> they have been (mostly!) just working great.
>>
>> If you are still using those old'' engines I'd suggest you update to the
>> latest which gets rid of the silly error message about latexmk not finding
>> a bib file (unless it's in the working directory).
>>
>> Good Luck,
>>
>> Herb Schulz
>> (herbs at wideopenwest.com)
>>
>>