On Sat, 2010-02-13 at 22:02 +0000, brian m. carlson wrote: > On Sat, Feb 13, 2010 at 09:04:38PM +0100, Soeren Sonnenburg wrote: > > On Sat, 2010-02-13 at 18:47 +0000, brian m. carlson wrote: > > > I don't see this behavior. I'm using cups 1.4.2-8 and have no problems. > > > Can you perhaps send the relevant parts of /var/log/cups/error_log ? > > > Also, what printer are you using and how is it set up (an IP printer, > > > printing to another CUPS server, local USB printer, etc.)? > > > > it is an ip printer. cups from stable works reliably... > > > > what other info do you need? > > The make and model of the printer would be helpful. So would the output > of "lpstat -t -p <printer-name>" (substituting the actual printer name), > and the relevant parts of the cups error log. Also, anything else that > you think might be relevant: if you configured cups or the printer in an > unusual or special way, those settings, for example. This does not happen with just a single printer, but the 2 postscript network printers I have here (HP Color LaserJet 4700 and a xerox phaser 6180dn). The HP is accessed via lpd:// and the xerox via socket://ip:9100 > Ideally, if I had the printer in question, I would have enough > information to be able to reproduce the problem. At the moment, I don't > even know whether I own such a printer (since I don't know what type it > is), and as I said, cups works for me. Since this is an RC bug, I'd > like to have the maintainers and other RC bug-fixers be able to have all > the information they need at hand to solve the problem. There is nothing unusual in my settings (I just added the printers... - default settings duplex). My guess is that the sole cause is pstopdf - I mean printing works as soon as I downgrade to cups from stable. Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962
Attachment:
signature.asc
Description: This is a digitally signed message part