OK, thanks for the update, Scott. I think there is enough information in this report now that it can be send to the programmers. For their ease, I will add a summary here. Please feel free to add any corrections.
-----------------------
SUMMARY:
Ubuntu version 16.04
16.04 (cups 2.1.3-4ubuntu0.5). system-config-printer-common 1.5.7+20160212-0ubuntu2. Hplip 3.16.3+repack0-1.
Problem is reproducable by the bug reporter. All print jobs from many different applications
Bug triager is unable to reproduce the bug.
Steps to reproduce:
1. Print an any document from an any application's print dialog (e.g. evince, Okular, GIMP, ReText,...).
2. Printing does not happen.
3. Open "system-config-printer”
4. Open the printer's print queue
5. All documents in the queue are processed, i.e. printed immediately.
Expected behaviour: the document prints immediately.
Actual behaviour: the document is held in the queue until the print queue is opened through "system-config-printer.”
Additional notes:
Printer is a RICOH MP C3003 situated on a large network.
CUPS interface on local computer indicates that job is stopped but “release job” button is ignored.
Opening the queue in “system-config-printer” on local computer immediately starts the job.
Reporter has uploaded tail of access.log which mentions authentication successful, only after the reporter opened the queue in “system-config-printer”
-----------------------
OK, thanks for the update, Scott. I think there is enough information in this report now that it can be send to the programmers. For their ease, I will add a summary here. Please feel free to add any corrections.
------- ------- ------- -- config- printer- common 1.5.7+20160212- 0ubuntu2. Hplip 3.16.3+repack0-1.
SUMMARY:
Ubuntu version 16.04
16.04 (cups 2.1.3-4ubuntu0.5). system-
Problem is reproducable by the bug reporter. All print jobs from many different applications
Bug triager is unable to reproduce the bug.
Steps to reproduce: config- printer”
1. Print an any document from an any application's print dialog (e.g. evince, Okular, GIMP, ReText,...).
2. Printing does not happen.
3. Open "system-
4. Open the printer's print queue
5. All documents in the queue are processed, i.e. printed immediately.
Expected behaviour: the document prints immediately.
Actual behaviour: the document is held in the queue until the print queue is opened through "system- config- printer. ”
Additional notes: config- printer” on local computer immediately starts the job. config- printer” ------- ------- --
Printer is a RICOH MP C3003 situated on a large network.
CUPS interface on local computer indicates that job is stopped but “release job” button is ignored.
Opening the queue in “system-
Reporter has uploaded tail of access.log which mentions authentication successful, only after the reporter opened the queue in “system-
-------
Triager searched for dups - none found.