DurvalMeneze, please post always into the bug report, so that other users see the process of the bug fix. I cite your mail below.

As reactivating the Foomatic accounting facility solves the problem, I will mark the foo2zjs targets invalid. The changes on Foomatic fixed this bug.

-------------------------------------

Hello Till,

On Wed, Jul 18, 2007 at 09:36:40AM -0300, Durval Menezes wrote:
> > On Wed, Jul 18, 2007 at 10:25:29AM -0000, Till Kamppeter wrote:
>> > > Your solution will fix page accounting only for the foo2zjs drivers
>> > > while many other drivers will stay without.
> > 
> > I was aware that the solution only applied to foo2zjs, but I did not
> > know that the problem was so widespread among other drivers.
> >
>> > > foomatic-rip, a filter used for integrating arbitrary printer drivers
>> > > with CUPS (and other printing systems) has support for page accounting,
>> > > but Debian maintainers turned it off by default due to problems with
>> > > some drivers.
>> > > 
>> > > To activate it, enter
>> > > 
>> > > sudo dpkg-reconfigure foomatic-filters
>> > > 
>> > > and answer the third question with "Yes".
>> > > 
>> > > Try to print now with an unpatched foo2zjs driver. You should get the
>> > > page accounting. If you do not get it, or if extra blank pages come out,
>> > > please tell here.
> > 
> > Thanks for the tip. I will try it next time I'm at this machine
> > (Saturday morning) and will let you know.

Just tried it (sorry for taking that long: busy weekend of a busy week),
and it DID work, and also it DID NOT print any extra blank pages. To sum
it up: turning accounting on in foomatic-rip indeed solved the problem
when using the old (unfixed) foo2zjs, without any ill-effects that I
can detect, surely no extra blank pages.

Just a small correction: on my system (Ubuntu 7.04 "Feisty") the
dpkg-reconfigure dialog was as follows:
		
	- Printer spooler backend for foomatic
		-> options: cups, lpd, lprng, pdq, ppr, direct;

	- Enable logging debug output into a logfile (INSECURE)
		-> Options: Yes, No;

	- Page with explanation about the ghostscript interpreter
	  selection;
		-> "Option": Ok;

	- Ghostscript interpreter to be used by Foomatic:
		-> Options: gs, gs-gnu, gs-esp, gs-afpl, Custom;

	- Enable PostScript accounting for CUPS?
		-> Options: Yes, No;

So, the question that I had to respond with Yes was the fourth
(or the fifth, if you count the "Ok" on the ghostscript interpreter
explanation page), and not the third.

Best Regards,
-- Durval Menezes (durval AT tmp DOT com DOT br, http://www.tmp.com.br/)
> > Best Regards,
> > -- 
> >    Durval Menezes (durval AT tmp DOT com DOT br, http://www.tmp.com.br/)
> > 
>> > > 
>> > > ** Changed in: foo2zjs (Ubuntu)
>> > >        Status: New => Incomplete
>> > > 
>> > > ** Changed in: foo2zjs (upstream)
>> > >        Status: New => Incomplete
>> > > 
>> > > ** Also affects: foomatic-filters (Ubuntu)
>> > >    Importance: Undecided
>> > >        Status: New
>> > > 
>> > > ** Changed in: foomatic-filters (Ubuntu)
>> > >        Status: New => Incomplete
>> > > 
>> > > ** Also affects: foomatic-filters (upstream)
>> > >    Importance: Undecided
>> > >        Status: New
>> > > 
>> > > ** Changed in: foomatic-filters (upstream)
>> > >        Status: New => Incomplete
>> > > 
>> > > -- 
>> > > CUPS page accounting not working
>> > > https://bugs.launchpad.net/bugs/126139
>> > > You received this bug notification because you are a direct subscriber
>> > > of the bug.