Bug 245552 - Can't cancel print job waiting in queue
Summary: Can't cancel print job waiting in queue
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-25 11:55 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-06-25 15:22:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
CUPS Bugs and Features 2424 0 None None None Never

Description Dominik 'Rathann' Mierzejewski 2007-06-25 11:55:02 UTC
Description of problem:
It's impossible to cancel a print job waiting in a remote LPD queue, because
print jobs submitted locally disappear from local queue almost instantly and
CUPS doesn't show remote queue contents like for example LPRng does.

Version-Release number of selected component (if applicable):
1.2.10-3.fc6

How reproducible:
Always.

Steps to Reproduce:
1. Configure local CUPS queue for a remote LPD (LPRng) printer
2. Submit a print job when remote printer is still printing something else
  
Actual results:
The print job disappears from local print queue almost immediately and it's
impossible to cancel it, because CUPS-provided lpq doesn't support remote
LPD-compatible servers.

Expected results:
lpq should either show the submitted job in the local queue until it is
completed or lpq should show remote queue contents and allow their control, per
RFC-1179. If it claims to be a lpq replacement, then it should be compatible.

Additional info:
I would replace CUPS with LPRng, but gtkprint is broken and doesn't show LPR
printers from printcap, like libgnomeprint did.

Comment 1 Tim Waugh 2007-06-25 15:22:38 UTC
Tracking upstream bug report.


Note You need to log in before you can comment on or make changes to this bug.