Bug#510857: Cups problem

[Armin Faltl <armin.faltl@aon.at>]

Hello Adrian,

I now tried to reproduce the behaviour with "LogLevel debug" set.
I'm sorry to disappoint you - after having set the option to debug
(with no verification this is the cause), I can't reproduce the
problem any longer - it vanished, i.e. the PDF-files now print with
command lp(1).
To select short pdf-files for testing I made something that may
have influenced this process: I installed AdobeReader_deu-8.1.3-1.i386.deb
from Adobe WEB-site. Since not being able to reproduce the bug
any longer, I purged this package but printing PDFs still works.
I did not try to print a pdf-file today, before installing this.

In hindsight, this may have happened after rebooting after reinstalling
the printer or any time after that esp. updates ?
From the CUPS web-interface I printed a test page, before trying lp(1)
as normal user - job shows up as 'guest' in /var/log/cups/page_log

How can I create the part of the bug-report telling the debian packages
without making a new report, to verify it's still the same or changed
system?

I attach the error_log from this successful print, in case it gives
you any information. The file '/etc/cups/pdftops.conf' still does not exist,
and it appeared as message for the jobs before I set 'debug', yet 
printing worked
today and I didn't try to print a pdf-file between creation of the bug 
report and
yesterday. In /var/log/cups I found the the old log messages: skimming 
through
them suggests, that the info for jobs 20-23 is lost or not present, 
while I saw
it in the HTML-interface before I set 'debug' indicating something about
'/etc/cups/pdftops.conf'.

Best Regards, Armin Faltl

P.S.: I set the bug to grave, since not being able to print a very 
common file format
on a postscript printer appeared severe to me - now I feel somewhat strange.

Adrian von Bidder wrote:
> Hi,
>
> (note to self: since I've successfully printed from both new lenny installs 
> and systems upgraded from something similar to etch I doubt this 
> deserves "grave" serverity.)
>
> Can you add log output from cups with "LogLevel debug" in cupsd.conf, 
> please?  Cups is extremely reluctant to disclose the real cause of the 
> problem otherwise...
>
> cheers
> -- vbi
>
>

Attachment: cups.error_log.bz2
Description: application/bzip

Attachment: error_log.1.gz
Description: GNU Zip compressed data

Attachment: error_log.2.gz
Description: GNU Zip compressed data

Attachment: error_log.3.gz
Description: GNU Zip compressed data

Attachment: error_log.4.gz
Description: GNU Zip compressed data

Attachment: error_log.5.gz
Description: GNU Zip compressed data

Attachment: error_log.6.gz
Description: GNU Zip compressed data