https://bugzilla.novell.com/show_bug.cgi?id=864313
https://bugzilla.novell.com/show_bug.cgi?id=864313#c1
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
InfoProvider| |jnelson-suse@jamponi.net
Platform|Other |All
Found By|--- |Community User
OS/Version|Other |openSUSE 13.1
--- Comment #1 from Johannes Meixner 2014-02-18 09:55:28 CET ---
Jon Nelson,
please provide feedback whether or not it works for you
with CUPS from the OBS project "Printing" both on the
server and at least on one client (cf. bnc#864312).
If CUPS from the OBS project "Printing" does not work,
you need to provide exact information of your printing setup
both on the server and on the client and your network setup, cf.
http://en.opensuse.org/SDB:How_to_Report_a_Printing_Issue
In particular I need CUPS debug messages both on the server
and on the matching client for exactly one such job that
disappears - please no complete /var/log/cups/error_log files
instead only what belongs to one single disappearing job.
FYI:
When a job disappears it usually means that for CUPS everything
was "successful" because CUPS would only remove the job when
it was "successful" - i.e. when CUPS did not notice an error.
For an example how a job could finish without a printout
see "What is a CUPS backend and how does it work?" at
http://en.opensuse.org/SDB:CUPS_in_a_Nutshell that reads:
----------------------------------------------------------------------
The print system considers the print job as completed when the
backend is finished. The backend is finished when the transmission
to the recipient is completed. If the further processing at the
recipient fails (e.g., if the printer is not able to print the
printer-specific data), this will go unnoticed by the print system.
----------------------------------------------------------------------
--
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.