Bug 239748
| Summary: | system-config-printer does not set or honour job-hold-until setting as set by lpoptions | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ben Li <benli> | ||||
| Component: | system-config-printer | Assignee: | Tim Waugh <twaugh> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 0.7.63.2-2.fc6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-07-30 11:13:03 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 239776 | ||||||
| Bug Blocks: | 207681 | ||||||
| Attachments: |
|
||||||
|
Description
Ben Li
2007-05-10 22:29:30 UTC
The real problem here is the crash. The rest is an unfortunate confusion caused by the two systems of providing job defaults. The older system, lpoptions, sets job defaults on *client* systems, the machines that the print jobs are sent from. /etc/cups/lpoptions is read by libcups when sending a job to a CUPS server. Yes, this may be on the same machine, but commonly the CUPS server is a separate machine altogether, and in this case the job defaults need to be set on all of the client machines. The newer system is network default options, and the options are stored in the *server* configuration. Incoming jobs have those default options applied if they are not already set by the client. To set a network default option from the command line you can use 'lpadmin [-h server] -p printer -o option=value'. The system-config-printer tool in Fedora Core 6 uses the network default options method exclusively, while in Fedora Core 5 and earlier the older lpoptions method was used (network default options are new to CUPS 1.2). I haven't been able to reproduce that crash though. Can you get it to happen again? If so, please make a note of exactly what steps you took. Thanks. Created attachment 154576 [details]
crash dump for system-config-printer when attempting to remove a printer option
Thanks for the insights about the changes. I suspected something like that was happening, although the fact that from one action some changes took, while others didn't, threw me off. Steps to reproduce the system-config-printer crash: 1. install FC6 from DVD 2. yum update cups* 3. yum update system-config-* 4. run system-config-printer as root 5. set up a new ipp printer 6. add job-hold-until option using job options tab, with value of indefinite 7. click apply 8. close system-config-printer 9. run system-config-printer 10. select printer set up in 5 11. click job options tab 12. click remove next to job-hold-until 13. click apply At this point, system-config-printer crashes with the attached dump. Thanks for the detailed instructions. From the backtrace I got from a core-dump with MALLOC_CHECK_=2 set in the environment, I think this is to do with the table resizing on that screen. Fedora 7 will have a re-worked version of that screen, although the specific case of job-hold-until doesn't work there for a different reason. :-/ Is job-hold-until the option you need to set on that queue? I'm curious to know the reason you mention that particular option -- do you want queued jobs to be individually approved by an administrator or something? Yes, we're using job-hold-until as part of our DiscoverStation multi-user public computing solution to enable staff to manually release print jobs through a web-based AJAX interface. Holding print jobs also enables us to do some neat tricks with dbus to notify users of print job size and cost to allow them to abort unwanted/broken/excessive print jobs before they hit the printer (in both the paid and the non-print cost recovery scenarios). Regarding the crash, we're currently advising customers to delete and recreate the printer instead of fiddling with the job options if they want to transition from gated printing to free printing. (Wow, cool stuff!) My plan for fixing this is to implement the missing bits in the Fedora 7 package that will make it work, then upgrade the Fedora Core 6 package to match. Unfortunately it means that the "Job Options" screen layout will change in FC6, but it is much more robust and easier to understand. |