Print Job with Authentication is postponed until queue is opened manually

[brandon211]

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”
-----------------------

Triager searched for dups - none found.

(original description follows)

I am connected to a print host requiring authentication. The authentication data is already stored in CUPS. I can issue a new print job and the printer icon in the panel appears, but the job isn't started, until I open the queue of the respective printer.
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CupsErrorLog:
 E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of /var/cache/cups/job.cache.
 E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of /var/cache/cups/job.cache.
 E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of /var/cache/cups/job.cache.
 E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of /var/cache/cups/job.cache.
 E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of /var/cache/cups/job.cache.
CurrentDesktop: UnityDistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2015-09-15 (1077 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
Lpstat:
 device for 0_prost: lpd://prost.uni-koblenz.de/
 device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14
 device for MFC9332CDW: dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390
MachineType: LENOVO 20BX000XGE
Package: cups 2.1.3-4ubuntu0.5
PackageArchitecture: amd64
Papersize: a4
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', '/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MFC9332CDW.ppd: Permission denied
 grep: /etc/cups/ppd/0_prost.ppd: Permission denied
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
Tags: xenial
Uname: Linux 4.15.0-30-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-04-22 (857 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp vboxusers
_MarkForUpload: True
dmi.bios.date: 09/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET66WW (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BX000XGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BX000XGE
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1638634/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

Absolutely no reaction since nearly 4 months... ?

[gf (gf-interlinks-deactivatedaccount)]

Hello Brandon,
Thank you for submitting this bug and reporting a problem with cups. You made this bug report some time ago and Ubuntu has been updated since then.

Could you confirm that this is no longer a problem and that we can close the ticket?
If it is still a problem, are you still interested in finding a solution to this bug?
If you are, could you let us know, and in the current version, run the following (only once):
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this particular issue.

Thank you again for helping make Ubuntu better.
G
[Ubuntu Bug Squad volunteer triager]

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

apport information

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

As sad as it is: this bug in fact has not been received any attention since I filed it roughly two years ago.

It *is* still a problem an I am *still* interested in finding a solution.
I executed apport as requested.

As I do not know which "other logs" could be relevant for this issue, I did not submit any further logs.

If there is anything I can do to further investigate this issue or to check, please let me know.

[gf (gf-interlinks-deactivatedaccount)]

Hi Brandon. Thanks for the update and the apport info. I'll look at next steps.
Take care
:)
G

[gf (gf-interlinks-deactivatedaccount)]

Hi Brandon,
Thanks in advance for your patience on my enquiries regarding this ticket. I am clarifying the issue for the programmers.

Could you tell me:
Do all print jobs cause the problem?
What application are you printing from?
What kind of files are you printing (docs, pdfs, large/small size files)?

Just trying to narrow down the problem.
Take care
:)
G

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

Yes, all print jobs cause the problem.
I print for example from evince, Okular, LibreOffice
I print all kinds of files you mention.

[gf (gf-interlinks-deactivatedaccount)]

Thanks for the information, Brandon. More questions...

Did this work in a previous version of Ubuntu?

You mention a print host. Is it another computer with Ubuntu on it? If so, what is the version of cups on the print host?

And when you open the print queue, are you opening it on your local computer or on the print host?

And just to confirm, it is a Brother MFC-9332CDW - ricoh14 printer?

Can you give me the exact steps you take to produce the problem?

Thanks
G

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

> Did this work in a previous version of Ubuntu?

I don't remember, this is >2,5 years from today, but I'm relatively sure that it didn't work back then also.

> You mention a print host. Is it another computer with Ubuntu on it? If
> so, what is the version of cups on the print host?

Yes, this is another host (why should I have to authenticate otherwise?). I don't know the OS of this system since it is run by operators.
According to its webinterface, the CUPS version is: 1.5.4.

> And when you open the print queue, are you opening it on your local
> computer or on the print host?

I open the queue on my computer.

> And just to confirm, it is a Brother MFC-9332CDW - ricoh14 printer?

No, there cannot be such thing as a "Brother ricoh" printer, as these are two different companies.

The Brother MFC-9332CDW is used directly via LAN (at a different location) and works just fine.

ricoh14 is the shortname of the printer in question. The exact printer model is:

> Can you give me the exact steps you take to produce the problem?

1. Print an arbitrary document from an arbitrary 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.

While re-reading my original bug report, it came to my mind that it may have been ambiguous what I meant by "open print queue". I *did not* mean the queue in CUPS but what I meant is the queue view available via GNOME (see above).

Today I checked what happens when I take a look at the queue via CUPS.
The job is listed there with the status "stopped" (notice that I translate the notions because my system runs in German).
For controlling the job CUPSs offers me three buttons:
- release job ("freigeben")
- delete job
- move job

When I choose the first one, nothing happens, i.e. the message "job was released" is shown but the state does not change.

I then start system-config-printer and only when I open the queue of the exact printer that should print, the print job is started immediately.

I also tail'ed /var/log/cups/access.log today when I tested it. The log is attached.
You can see the excerpt begins after the print job has been issued (Print-Job successful-ok). Nothing happens and after a time I open the printer's queue (system-config-printer). Upon opening the tool, the three "Create-Printer-Subscriptions" messages appear. Only when I open the queue, the message "CUPS-Authenticate-Job successful-ok" comes up and that is the moment the printer actually starts printing.

[brandon211 (brandon211-deactivatedaccount-deactivatedaccount)]

The printer model is a RICOH MP C3003.

[gf (gf-interlinks-deactivatedaccount)]

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”
-----------------------

Triager searched for dups - none found.

[gf (gf-interlinks-deactivatedaccount)]

Sorry, Brandon. I wrote your name wrong. I meant: Brandon
:)
G

[C de-Avillez (hggdh2)]

setting to Triaged/Low per request on #ubuntu-bugs. Description updated as in comment #24.

[gf (gf-interlinks-deactivatedaccount)]

Thanks for changing the status and importance, C.
Have a great day!
:)
G