https://bugzilla.novell.com/show_bug.cgi?id=337665#c9
Ben Bucksch changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #9 from Ben Bucksch 2007-10-30 05:40:28 MST ---
We barely use the HP, so I don't know whether it happens there.
I bought the Samsung ML-2010 specifically for Linux. It's one of the few
desktop printers which are officially supported. Don't tell me that it's "not
good" either.
<quote src="http://en.opensuse.org/SDB:CUPS_in_a_Nutshell#The_Backends">
If the data transmission to the recipient fails (usually after several attempts
by the backend), the backend will report an error to the print system (more
precisely, to cupsd). The backend decides if and how many attempts make sense
before it reports that the data transmission has failed. As further attempts
would be futile, cupsd disables printing on the affected queue. After
eliminating the cause of the problem, the system administrator must reenable
printing with /usr/bin/enable (for CUPS 1.1 - i.e. up to Suse Linux 10.1) or
with cupsenable (since CUPS 1.2 - i.e. since openSUSE 10.2)."
</quote>
The last 2 sentences *are* the bug. If "out of paper" is an error, that would
result in the printer being disabled, i.e. the bug.
Even when the USB cable was accidentally ripped out (somebody tripped over the
cable, or rearranged the printer/computer etc.) and it is plugged back in by
the user, he expects it to work again, not to need a root password and
re-"enable" a printer in some admin console. In other words, removing the USB
cable and adding paper is a normal operation done by normal users and must not
need root password, admin consoles or any special action at all.
Automated "Resume" (e.g. when in your casee it might re-appear
at the USB after the "paper out") is often asked for on the CUPS
mailing list but the answer is always the same:
In that case, the answer is always wrong. The fact that it's often asked should
show you that there's something wrong with the software, not the users.
As the original description states: Please change the default policy. Average
users will just hit the print button again (as you can see from my error log,
which accumulated 10 print jobs, because my father kept hitting "print" when
nothing happened, which is a normal reaction). Default settings should be for
average desktop users, not big sites with remote printers. Big sites can easily
change settings, normal users can not, they don't even know the setting.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.