> 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.
** Attachment added: "cupsaccesslog.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638634/+attachment/5184454/+files/cupsaccesslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638634
Title:
Print Job with Authentication is postponed until queue is opened
manually
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638634/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
