Xwatermark Package Stopped Working

[David Lentini]

10:14 AM (less than a minute ago)
Hi, All!

I've been using xwatermark with TL 2014 (64-bit Kubuntu 14.04) without problems until yesterday after I ran my daily update.

Here's my example:

\documentclass[a4paper, 12pt]{article}
\usepackage[printwatermark]{xwatermark}

\begin{document}

\newwatermark[allpages,fontfamily=pag,color=gray!25,angle=45,scale=5, xpos=-30,ypos=20]{DRAFT}

What is claimed:

\begin{enumerate}
\item Blah

\item Blah blah

\item Blah blah blah

\end{enumerate}
\end{document}

Here's the error:

ERROR: Undefined control sequence.

--- TeX said ---
l.27 \xwm@secstopagerange
{{1}{1},{2}{1},{2}{1},{2}{1},{3}{2},{4}{2},{5}{2},{...
--- HELP ---
TeX encountered an unknown command name. You probably misspelled the
name. If this message occurs when a LaTeX command is being processed,
the command is probably in the wrong place---for example, the error
can be produced by an \item command that's not inside a list-making
environment. The error can also be caused by a missing \documentclass
command.

I found a .xwm file (scratch file?) and the expected .pdf, but the .pdf won't open.

[Dan Luecking]

On Fri, 11 Jul 2014 07:16:43 -0700 (PDT), David Lentini
<david....@gmail.com> wrote:

>
>10:14 AM (less than a minute ago)
>Hi, All!
>
>I've been using xwatermark with TL 2014 (64-bit Kubuntu 14.04) without problems until yesterday after I ran my daily update.
>
>Here's my example:
>
>\documentclass[a4paper, 12pt]{article}
>\usepackage[printwatermark]{xwatermark}
>
>\begin{document}
>
>\newwatermark[allpages,fontfamily=pag,color=gray!25,angle=45,scale=5, xpos=-30,ypos=20]{DRAFT}
>
>What is claimed:
>
>\begin{enumerate}
> \item Blah
>
> \item Blah blah
>
> \item Blah blah blah
>
>\end{enumerate}
>\end{document}
>
>Here's the error:
>
>ERROR: Undefined control sequence.
>
>--- TeX said ---
>l.27 \xwm@secstopagerange
> {{1}{1},{2}{1},{2}{1},{2}{1},{3}{2},{4}{2},{5}{2},{...
>--- HELP ---

This seems unlikely. Your example file has only 17 lines and
none of them look like that. Also, xwatermark.sty itself has no such
line in it. I ran your example file and got only the following error:

! Undefined control sequence.
<argument> ...e \@tempdima \@parboxrestore \color

This was easily rectified by adding
\usepackage{xcolor}
to the preamble

If you really get the error you claim just from this short
example, you should also mention what version of
xwatermark.sty you are using, as it would seem the only other
file where this command would occur.


Dan
To reply by email, change LookInSig to luecking

[Dan Luecking]

On Mon, 14 Jul 2014 11:23:05 -0500, Dan Luecking <Look...@uark.edu>
wrote:

>On Fri, 11 Jul 2014 07:16:43 -0700 (PDT), David Lentini
><david....@gmail.com> wrote:
>
>>
>>10:14 AM (less than a minute ago)
>>Hi, All!
>>
>>I've been using xwatermark with TL 2014 (64-bit Kubuntu 14.04) without problems until yesterday after I ran my daily update.
>>
>>Here's my example:
>>
>>\documentclass[a4paper, 12pt]{article}
>>\usepackage[printwatermark]{xwatermark}
>>
>>\begin{document}
>>
>>\newwatermark[allpages,fontfamily=pag,color=gray!25,angle=45,scale=5, xpos=-30,ypos=20]{DRAFT}
>>
>>What is claimed:
>>
>>\begin{enumerate}
>> \item Blah
>>
>> \item Blah blah
>>
>> \item Blah blah blah
>>
>>\end{enumerate}
>>\end{document}
>>
>>Here's the error:
>>
>>ERROR: Undefined control sequence.
>>
>>--- TeX said ---
>>l.27 \xwm@secstopagerange
>> {{1}{1},{2}{1},{2}{1},{2}{1},{3}{2},{4}{2},{5}{2},{...
>>--- HELP ---
>
>This seems unlikely.

I have since been able to reproduce this error. The above line
(or one like it) occurs in the .aux file. If I run your example
file and then run it again with
\usepackage[printwatermark]{xwatermark}
commented out, the error occurs upon reading the .aux file at
\begin{document}.

However, it is not in the above format, nor is it on line 27 as
your claimed error message says.

> Your example file has only 17 lines and
>none of them look like that. Also, xwatermark.sty itself has no such
>line in it. I ran your example file and got only the following error:
>
>! Undefined control sequence.
><argument> ...e \@tempdima \@parboxrestore \color
>
>This was easily rectified by adding
> \usepackage{xcolor}
>to the preamble
>
>If you really get the error you claim just from this short
>example, you should also mention what version of
>xwatermark.sty you are using, as it would seem the only other
>file where this command would occur.

When you provide a minimal example file, you should supply
the error mesage that that *it* produces. It also helps to
describe precisely the circumstances that produce the error
message: In addition to the minimal example file, record
what sequence of actions on your part led to the error message.

[David Lentini]

Thanks for your help, Dan. I certainly tried to be as complete in
reportin the error as possible. Fortunately, I suppose, I don't have
to report LaTeX errors often. :-)

I'm runing TL 2014. The xwatermark.sty file indicates it's version
1.5.2d (23 October 2012).

As far as the circumstances, previously the document executed without
any error. After upgrading TL (which I do daily) on 11 July, the
trouble started. I've also run into in on my Mac.

Any suggestions? Can I provide more information?

Thanks,
David

[David Lentini]

I seem to have (somewhat) fixed the problem. I added the xcolor
package and deleted the "pch" fontfamily, leaving that value blank.
The document compiles, with "DRAFT" in a different typeface. However,
the location of the watermark is now shifted on the second page.

[Dan Luecking]

On Tue, 15 Jul 2014 09:34:36 -0400, David Lentini
<david....@gmail.com> wrote:

>I seem to have (somewhat) fixed the problem. I added the xcolor
>package and deleted the "pch" fontfamily, leaving that value blank.
>The document compiles, with "DRAFT" in a different typeface. However,
>the location of the watermark is now shifted on the second page.

1. Your example file has only one page, so you are not
describing the example you gave us to work with.
2. Your example file doesn't contain fontfamily=pch so
you are again not describing the example you gave us.

Please, your descriptions should refer to a supplied example
that exhibits the problems.

In any case, I've added a second page to the example you posted,
tried with fontfamily=pch and no fontfamily at all, and still
no error messages (after adding \uspackage{xcolor}, which is
certainly required for the color=gray!25 option). Also, there
is no shifting on the second page in any of these cases.

I can only suggest you try harder to create a small example that
really does cause the problems you describe. Or supply a link to
your actual file (but only if you cannot reproduce the errors
with a small example).

>> As far as the circumstances, previously the document executed without
>> any error. After upgrading TL (which I do daily) on 11 July, the
>> trouble started.

When I said "describe _precisely_ the circumstances that produce
the error" I meant supplying the actual commands typed (and/or
sequence of mouse clicks) and their consequences. For example:

"I ran
pdflatex test.tex
after updating TeX Live and the errror meassage
! Undefined control sequence
\color
l.21 \end{document}

?
occurred. I deleted all generated files test.aux, test.xwm,
test.log, test.pdf, added `\usepackage{xcolor}' and again
tried
pdflatex test.tex
This time there were font warnings but no errors. But then
I ran
pdflatex test.tex
again and I get the following errors..."

Or whatever actually occurs.