# Conflicting situation from concurrent use of pdfpages and pgfpages in beamer [closed]

From my beamer slides I produce multi slide per page pdfs which are easier for printing.

Things went fine all these years until I used pdfpages and pgfpages in the same file. Here is the stripped down minimal file (from a shell script generated version),

\documentclass{beamer}

\usepackage{pdfpages}

\usepackage{pgfpages}
\pgfpagesuselayout{4 on 1}[a4paper,border shrink=2.5mm,landscape]

\begin{document}

\includepdf{mypdf.pdf}

\end{document}

Whenever I pdflatex this file, I get an error message in the line of,

! Undefined control sequence.
<argument> \raise \ht \@tempboxa \hbox {}\AM@fbox
{\AM@ARBug@hook \AM@reflec...
l.16 \end{document}

I find that if either of pdgpages or pgfpages is omitted, things go fine.

Any suggestion will be appreciated.

-

## closed as too localized by egreg, Paul Gaborit, mafp, Werner, KurtFeb 12 '13 at 1:45

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

I get no error; this is my version of pdfpages: pdfpages.sty 2012/08/31 v0.4t. You can see it in the log file if you add \listfiles to the preamble of the .tex document. – egreg Feb 11 '13 at 10:48
My versions are pgfpages 2004/11/05 ver 0.01, pdfpages 2009/02/07 v0.4g, pdfTeX 3.1415926-1.40.10-2.2 (TeX Live 2009/Debian), Ubuntu 12.04 – Masroor Feb 11 '13 at 14:00
Mine too; what version of pdfpages do you have? – egreg Feb 11 '13 at 14:01
pdfpages 2009/02/07 v0.4g, please see my previous comment – Masroor Feb 11 '13 at 14:07
For the record, I get the same error using pdfpages in a beamer document, without knowingly using pgfpages. pdfpages version is pdfpages 2009/02/07 v0.4g Installing the newer version from CTAN made the error disappear. Thanks. – bli Mar 15 '13 at 18:15