cupsd.conf defaults need to allow reprint of jobs

Bug #343801 reported by Kemble Wagner
6
Affects Status Importance Assigned to Milestone
CUPS
New
Undecided
Unassigned
cups (Ubuntu)
Incomplete
Wishlist
Unassigned
system-config-printer (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: cups

if you see the screen shots in this thread http://ubuntuforums.org/showthread.php?t=820916 you will see what im talking about i think it would be much nicer if /etc/cups/cupsd.conf contained these 2 lines by default

# preserve last 50 print jobs

PreserveJobFiles Yes
MaxJobs 50

you can make max jobs higher but the "PreserveJobFiles Yes" is important as it allows users to reprint jobs that fail due to
various reasons. its handy and other distros are using this as a default option

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

pitti, WDYT, I think this configuration would make sense. And the hard disks of modern computers should be big enough to hold 50 print jobs, and it often happens that hardware problems like paper jams, toner out. or letter head paper loaded into wrong tray occur.

Revision history for this message
Martin Pitt (pitti) wrote :

Hm, I'm not really sure about this. Print jobs can get very big (my wife regularly has print jobs which are some 300 MB), and keeping 50 of those around is a fairly huge space hog.

cups is neither a backup nor a revision control system, and usually I would assume that you keep documents in their "source" form as well when you print them.

However, I do see the value of keeping the previous job, so as a compromise to enable by default, what do you think about

  PreserveJobFiles Yes
  MaxJobs 2

?

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

pitti, for me this is OK. This is mostly to quickly correct little mistakes (for example after having closed the app and so avoiding manu more clicks to get back to the file to be printed),

Revision history for this message
Kemble Wagner (oobe-trouble) wrote :

yes this will work ok for me i will change my cupsd.conf to reflect this just to see how it goes cant forsee any reason i would really need to access print jobs 47 from 18 days ago

Martin Pitt (pitti)
Changed in cups (Ubuntu):
assignee: nobody → pitti
status: New → In Progress
Revision history for this message
Martin Pitt (pitti) wrote :

After reading the documentation I'm not so sure about this. MaxJobs does not control the number of job files which are stored on disk (which we want to keep to a minimum, such as 1), but to the total number of jobs that can be put into the queue (which should be considerably larger than 1, it is 500 by default). But at the same time we don't want to permanently store the last 500 print jobs on disk.

Thus right now I don't see a setting to control what this bug asks for, or am I missing something?

Changed in cups (Ubuntu):
status: In Progress → Incomplete
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Pitti, you are right. Limiting MaxJobs limits the allowed number of jobs in the queue. So setting it to 2 or 3 will cuase problems. In gheneral a small office/home user could set it to 10 when preserving jobs, but a server user must keep it on a higher value, especially if he also wants to use quotas. So it depends highly on the users demands. Pitti you could post a feature request to CUPS for allowing different settings for the maximum of jobs allowed in the queue and the maximum of job files for completed/aborted jobs held on disk.

Looks like that we need to make these settings available in system-config-printer.

Changed in system-config-printer (Ubuntu):
importance: Undecided → Wishlist
Changed in cups (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Martin Pitt (pitti) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Waiting for upstream fix.

Changed in cups (Ubuntu):
assignee: Martin Pitt (pitti) → nobody
status: Incomplete → Triaged
Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

I tested in Ubuntu 10.04 and Ubuntu 10.10.

In the cups webinterface Server Settings it's possible to activate the "Preserve job print files" option, this adds PreserveJobFiles Yes to /etc/cups/cupsd.conf. Also the job history is preserved for 500 jobs by default and can be changed, this add MaxJobs # in /etc/cups/cupsd.conf.

In system-config-printer Server > Settings... > Advanced Server Settings it is also possible to select Preserve job files (allow reprinting) which add the PreserveJobFiles Yes to /etc/cups/cupsd.conf
Although the right-click Reprint option remains grayed out in system-config-printer-applet so doesn't allow reprint, but reprint works in the cups webinterface.

Till, Martin,
So it looks like cups and system-config-printer have gained support for reprint setting. OK to close this bug?

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Reported bug #675259 for the grayed out Reprint option in system-config-printer-applet.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Closed for system-config-printer. Option for job preservation is there and works. "Reprint" in job viewer staying gray is hyandled in new bug report.

Changed in cups (Ubuntu):
status: Triaged → Fix Released
Changed in system-config-printer (Ubuntu):
status: New → Fix Released
Changed in cups (Ubuntu):
status: Fix Released → Triaged
Revision history for this message
gf (gf-interlinks-deactivatedaccount) wrote :

Hello Kemble,
Thank you for submitting this feature/enhancement request for the hplip package. You made this request quite some time ago and Ubuntu has been updated since then.

Do you think this feature/enhancement is still needed or can we close this bug report?

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

Revision history for this message
gf (gf-interlinks-deactivatedaccount) wrote :

Sorry, I meant: ".. with the *cups* package."

Changed in cups (Ubuntu):
status: Triaged → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.