Ticket #503 (reopened enhancement)

Opened 12 years ago

Last modified 11 years ago

cups-lpq doesn't tell you about the most recent completed job

Reported by: geofft Owned by:
Priority: low Milestone: Upstream Utopia
Component: printing Keywords:
Cc: Fixed in version:
Upstream bug:

Description

dr-wily:~ geofft$ lpq -Pmassave
Printer: massave@mulch  'HP NW86-158'
 Queue: no printable jobs in queue
 Status: job 'fiona_yu@sp-res14+812' removed at 13:47:05.689
 Filter_status: done at 13:47:05.636
dr-wily:~ geofft$ lpq -Ptree-eater
tree-eater is ready
no entries

If your job prints quickly, it becomes confusing as to whether it actually printed or just disappeared into the ether.

Change History

comment:1 Changed 11 years ago by jdreed

  • Status changed from new to closed
  • Resolution set to wontfix

The complaint here is essentially "CUPS is not LPRng". If you disagree, re-open the ticket, but we need a better solution than "Convince CUPS to emulate LPRng"

comment:2 Changed 11 years ago by jdreed

  • Status changed from closed to reopened
  • Resolution wontfix deleted
  • Milestone set to Upstream Utopia

Fine, CUPS is not LPRng. So file an upstream ticket to make it LPRng. I'm not convinced that adding yet another patch to either our frankencups servers or our wrappers to support this feature is a good idea, but *shrug*.

Note: See TracTickets for help on using tickets.