After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 172965 - Cannot delete job from queue
Cannot delete job from queue
Status: RESOLVED WONTFIX
Product: gnome-cups-manager
Classification: Deprecated
Component: gnome-cups-manager
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2005-04-07 15:48 UTC by Ross Burton
Modified: 2012-02-28 15:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
a quick patch to add cups negotiation support (4.85 KB, patch)
2008-03-14 17:33 UTC, James F. Carter
none Details | Review

Description Ross Burton 2005-04-07 15:48:17 UTC
If I delete a job from a print queue, FOOBAR is printed on the console and
gnome-cups-manager hangs.
Comment 1 Ross Burton 2005-04-07 16:36:27 UTC
Note that if I do "lprm 4" in a console, lprm asks me for my password even if I
created the job.
Comment 2 Adonikam Virgo 2005-05-23 17:09:47 UTC
I get the same on two computers with different printers cancelling user jobs
with the error:
** (gnome-cups-manager:24701): WARNING **: FOOBAR

You can still cancel it with `cancel $job` using output from lpq.
Comment 3 Adonikam Virgo 2005-05-28 10:59:34 UTC
Steps:
Turn any connected printer off or disconnect it to hold job in queue.
On CLI:
Run command `gnome-cups-manager --version`.
Run command `gnome-cups-manager` as a non-root user.
In GUI:
Right-click an existing printer and select `Jobs`.
Left-click menu `Printer` and select `Print Test Page`.
Right-click displayed job and select `Cancel`.
On CLI:
View output.

IMHO this bug is of severity Major. Surely there is a dev that wants this
functionality.
Comment 4 Adonikam Virgo 2005-06-12 16:37:56 UTC
If anyone finds this (ignored) bug and needs a temporary fix, the following page
has information on allowing any user on the local network to delete print jobs -
this is not a secure method, but should be sufficient for casual desktop users.
http://adam.rosi-kessel.org/cups/cupsd.conf

Append the following extract in /etc/cups/cupsd.conf:
# This will allow anyone ... to cancel ... jobs without a password
<Location /jobs>
AuthType None
AuthClass Anonymous

Order Deny,Allow
Deny From All
Allow From 127.0.0.1
Allow From 192.168.0.*
</Location>

<Location /admin/?op=cancel-job>
AuthType None
Order Deny,Allow
Deny From all
Allow from 192.168.0.*
Allow From 127.0.0.1
</Location>

You then need to restart the cups server. On Debian systems you run
`/etc/init.d/cupsys restart` as root.
Comment 5 Adonikam Virgo 2006-06-11 20:56:03 UTC
*Update*
The problem in version 0.31 is that it prompts for the user password on the running console and the gui is unresponsive:

Password for $USER on localhost? 

This is on Debian with cups 1.2.1. Although it works by default, it does not if the job-cancellation authentication is explicitly set to AuthType Basic. The backtrace is available here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276175
Comment 6 Reinout van Schouwen 2007-09-14 10:21:04 UTC
Confirming this. 
Mandriva bug: http://qa.mandriva.com/show_bug.cgi?id=33529
Comment 7 Kjartan Maraas 2008-01-29 13:09:51 UTC
Moving all gnome-cups-manager bugs to new product. Filter on Kjartan's spring cleaning.
Comment 8 James F. Carter 2008-03-14 17:33:05 UTC
Created attachment 107307 [details] [review]
a quick patch to add cups negotiation support
Comment 9 James F. Carter 2008-03-14 17:39:10 UTC
(In reply to comment #8)
> Created an attachment (id=107307) [edit]
> a quick patch to add cups negotiation support
> 

sorry! somehow this ended up on the wrong bug. don't know how i managed that...
Comment 10 André Klapper 2012-02-28 15:53:09 UTC
"gnome-cups-manager" will not see active development anymore according to its
developers.
Closing this report as WONTFIX - Please feel free to reopen this bug report in
the future if anyone takes the responsibility for active development again.