[Pkg-cups-devel] Bug#502624: cups-pdf: "Test page" from web interface should use real user instead of 'anonymous'

[Martin-Éric Racine]

reassign 502624 cups
thanks

On Mon, Jan 26, 2009 at 12:52 PM, Volker Behr
<behr at physik.uni-wuerzburg.de> wrote:
> On Tue, 2008-12-23 at 22:06 +0200, =?UTF-8?Q? Martin-=C3=89ric?= Racine
> wrote:
>> > Otherwise one can't print a test page when 'anonymous' is disabled in
>> > cups-pdf configuraiton file. Moreover, no errors are reported either
>> > in web interface or log files in this case.
>>
>> > Looking at the completed jobs I conclude that Etch version used real
>> > users to print test pages. So, this sudden change after upgrade to Lenny
>> > confused me while I was trying to locate the printed test page in ~/PDF
>> > folder.
>>
>> This report seems to confuse too many issues. Let's divide those into
>> smaller blocks:
>>
>> 1. what user should be used to generate the test page? (a CUPS issue)
>
> ...and that's already the end of the story. Since CUPS-PDF has no means
> to determine whether a specific page is a CUPS test page (no, CUPS-PDF
> will never do an in-detail analysis of the contents of the PostScript
> passed to it) the test page will always be printed as the user CUPS
> chooses for printing it.
>
>> 2. where should the test page file be saved to? (a CUPS-PDF issue)
>
> This is solely determined by the user chosen at 1. (i.e. by CUPS).
>
>> 3. whether CUPS-PDF should be dependent upon the AnonUser being
>> enabled to produce a test page?
>> a) if yes, should it print an error message to alert the administrator
>> that, when AnonUser is disabled, it cannot produce the test page?
>> b) if not, which system user should be used to produce the test page?
>> (all those are CUPS-PDF issues)
>
> Once again: since I do not have any chance to tell a test page apart
> from a real print job, the statements made above fully apply. In case of
> denied anonymous accesses already now CUPS-PDF prints an "anonymous
> access denied" as INFO-message to its log file.
>
> Regards,
> Volker

As confirmed by the upstream author of CUPS-PDF, what system user is
called to make test printouts via the CUPS Web interface is not
dependent upon CUPS-PDF at all, since it's a generic feature of CUPS,
so I'm reassigning this bug to CUPS.

Martin-Éric