I get a very weird "error" just momentarily when I compile my document but when the compilation is finished it disappears and I have no errors or warnings. As you can see the "error" is huge and it keep going as there is a scrolling bar. This started happening the time that I used the \usepackage{steinmetz} and its command \phase{}. If I delete them then everything is ok. Why is this happenning and how can I fix it?

A MWE which has that problem when compiled:

\usepackage[top=0.7in, bottom=1.2in, left=0.8in, right=0.8in]{geometry}












$Y=|Y|\cdot e^{j\phi}=|Y|\phase{\phi}$


enter image description here

I don't know if this helps but these are the settings of my Texmaker:

enter image description here

After using the solution proposed by Ulrike Fischer all this "scary" warning disappears and in its place appears the following. It is of the same nature which means that it appears during compilation and disappears after the compilation is complete. What is that?

enter image description here

  • Are you trying to compile with pdfTeX rather than TeX? (pdfLaTeX rather than LaTeX.)
    – cfr
    Sep 12, 2014 at 21:01
  • I use XeLaTeX I don't know if that helps.
    – Adam
    Sep 12, 2014 at 21:06
  • Steinmetz relies on pict2e, and imho there is no xetex driver in pict2e. Sep 12, 2014 at 21:26
  • I get no error from a minimal document; and p2e-xetex.def is loaded. Tested with TeX Live 2014, 2013 and 2012.
    – egreg
    Sep 12, 2014 at 21:43
  • 2
    This picture is what I get, with no error. By the way, \everymath{\displaystyle} is not recommendable.
    – egreg
    Sep 12, 2014 at 21:54

1 Answer 1


As I mentioned in my comment, steinmetz loads pict2e, and this package needs to load the correct driver. The loading of the driver is done in pict2e.cfg which on miktex is from 2005 (completly outdated) and so doesn't load the suitable driver for xetex but the dvips driver instead. In Tex Live there is no problem. Make a bug report on the miktex site. A work-around for the problem is to force pict2e to load the correct driver:


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .