The above URL explains the problem, but basically, you can't delete print jobs via the web interface without first authenticating. In some cases, such as a small LAN where you trust everyone, or a public computer lab where people don't have the passwords, authentication is annoying or impossible. The attached ebuild introduces a USE flag to allow the desired operation. Specifically, the USE flag and included patch (from the URL) will ignore the owner of a CUPS job/entity when AuthType is set to "none". This allows the jobs to be deleted, if so configured. Reproducible: Always Steps to Reproduce: 1. Set up a CUPS print server 2. From a different computer, a workstation, submit a long print job 3. From that workstation, browse to http://server:631/jobs and try to cancel the print job. Actual Results: "Client-Error-Forbidden" error message Expected Results: Job should be successfully cancelled.
Related bug is bug 29470, which says "fixed" despite it not being fixed in the latest ebuilds.
Created attachment 39234 [details] Ebuild with new use flag Introduces package-specific USE flag "cupsignoreowner"
Created attachment 39235 [details, diff] This patch is turned on by the new use flag. Downloaded from http://bostoncoop.net/adam/cups/cups_patch_1.1.20
I don't think is a good ideia add this USE flag to cups. It's not safe imo. I will mark this as WONTFIX. Thanks
