[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#126170: marked as done (cupsys: unclear "Invalid printer settings!" error message)

Your message dated Sun, 1 Jun 2008 23:09:06 +0200
with message-id <20080601210906.GB6509@piware.de>
and subject line Cleaning up old bug reports
has caused the Debian Bug report #126170,
regarding cupsys: unclear "Invalid printer settings!" error message
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
126170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=126170
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cupsys
Version: 1.1.12-3

I tried printing to my Epson Stylus Color 850 for the first time in a
couple of months (the last time was in October). Now nothing came out of
the printer; in fact, nothing appeared to happen except that the job was
listed as "completed at <date>".  Digging a little further, I see in
/var/log/cups/error_log the following:


I [22/Dec/2001:14:25:04 -0100] Job 18 queued on 'epson' by 'root'.
I [22/Dec/2001:14:25:04 -0100] Started filter /usr/lib/cups/filter/texttops (PID 23642) for job 18.
I [22/Dec/2001:14:25:04 -0100] Started filter /usr/lib/cups/filter/pstops (PID 23643) for job 18.
I [22/Dec/2001:14:25:04 -0100] Started filter /usr/lib/cups/filter/pstoraster (PID 23644) for job 18.
I [22/Dec/2001:14:25:04 -0100] Started filter /usr/lib/cups/filter/rastertoprinter (PID 23645) for job 18.
I [22/Dec/2001:14:25:04 -0100] Started backend /usr/lib/cups/backend/parallel (PID 23646) for job 18.
E [22/Dec/2001:14:25:04 -0100] Invalid printer settings!


I have no idea what the invalid printer settings are, AFAIK I didn't
touch the settings since the last time the printer worked; only cupsys
et.al. was updated, so I naturally expect that to be the source of my
troubles :-)

My PC _has_ undergone a hardware transplant (new motherboard), but
escputil can still communicate just fine with the printer and also "date
> /dev/lp0" gives the expected result.

I've tried creating a new printer definition, and that works....
It looks like there's a problem when old definitions "disappear". The
original epson entry shows up as:

     EPSON Stylus Color 850, CUPS+GIMP-print v4.1.7

When creating the new one, the driver is:

     EPSON Stylus Color 850, CUPS+GIMP-print v4.1.99-b1

Perhaps there should be some mechanism to automagically upgrade the
driver definition in such situations?

My main complaint is that the error message is pretty useless, some more
info on what is invalid would be nice; also the jobs shouldn't be listed
as "completed" in the list of old jobs.

Another note: the time in the log is listed as "-0100", which is wrong;
it should be +0100 (MET). "date --rfc-822" also gives the expected +0100
(check the headers in this email for another example).


Thanks,
Paul Slootman

--- End Message ---
--- Begin Message --- 
Dear bug submitter,

This bug was reported against a very old version of cups (older than
in the current stable Debian version "Etch"). About a year ago,
Martin-Eric Racine asked for feedback whether the bug still applied to
the current Debian Etch version, but we did not get any feedback. In
order to not keep around old, hardware-specific, and inactive bugs
around forever, I close this bug now.

Please report back if you still experience the problem with the
current version in Etch; if you can test Lenny/unstable, that would be
highly appreciated, of course. I will reopen this bug then.

Thank you for your report!

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: