The warning continually appears and I always ignore it, but today I want to know how to deal with it.
My MWE is
\documentclass[14pt]{beamer}% http://ctan.org/pkg/beamer
\let\Tiny\tiny% http://tex.stackexchange.com/q/58087/5764
\usetheme{Berkeley}
\makeatletter
\beamer@headheight=1.5\baselineskip
\makeatother
\setbeamercolor{normal text}{bg=black!10}
\title[Title]{My title}
\subtitle{Subtitle}
\author{Author}
\institute[Institute]{My institute}
\date[Date]{My date}
\logo{\color{blue!50}\scalebox{2}{\TeX}} % you can % it
\begin{document}
\begin{frame}
\titlepage
\end{frame}
\section{A section}
\subsection{A subsection}
\begin{frame}
\frametitle{Frame title}
\framesubtitle{frame subtitle}
Some text
\end{frame}
\end{document}
and the output is as followed:
Package rerunfilecheck Warning: File `model.out' has changed.
(rerunfilecheck) Rerun to get outlines right
(rerunfilecheck) or use package `bookmark'.
)<C:/CTEX/MiKTeX/fonts/type1/public/amsfonts/cm/cmss10.pfb><C:/CTEX/MiKTeX/fon
ts/type1/public/amsfonts/cm/cmss12.pfb><C:/CTEX/MiKTeX/fonts/type1/public/amsfo
nts/cm/cmss17.pfb><C:/CTEX/MiKTeX/fonts/type1/public/amsfonts/cm/cmss8.pfb>
Output written on model.pdf (2 pages, 51454 bytes).
SyncTeX written on model.synctex.gz.
Transcript written on model.log.
gbk2uni, version 0.22, initially implemented by cxterm and ZLB in Jan. 2003
enhanced by hooklee in Mar. 2003.
please visit www.ctex.org and www.chinatex.org for more information.
gbk2uni model.out is finished!
_____________________________________________________________________
PDFLaTeX Compilation Report (Pages: 2)
Errors: 0 Warnings: 1 Bad Boxes: 0
_____________________________________________________________________
\usepackage{bookmark}it works – ytyyutianyun Mar 27 '14 at 04:32bookmarkthere is a warning in the first run and in each run, where the bookmarks are changed. In the second run of the MWE I do not have a warning. – Heiko Oberdiek Mar 27 '14 at 05:24\usepackage{bookmark}, I also get the warning in every run – lucidbrot Oct 04 '18 at 18:59bookmarksfixes some problems because of its improved algorithm. That not using it does not fix these problems seems pretty clear, doesn't it? Please, make a new question with a minimal working example (MWE) with a clear description, how it is compiled and about the error. – Heiko Oberdiek Oct 04 '18 at 20:32rerunfilecheck. The other 0.01% needs investigation, that will not happen if there is nothing to investigate (MWE, versions, ...) and no volunteers that investigate. – Heiko Oberdiek Oct 04 '18 at 21:36