[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#736089: cups-client: Modifying or reinstalling a queue with lpadmin is unreliable



On Thu 23 Jan 2014 at 17:28:19 +0000, Brian Potkin wrote:

> https://www.cups.org/str.php?L4353

Mike Sweet writes:

   Sorry, I tried everything I could to reproduce this and was
   unable.  Even a script that just continuously flipped between
   two PPDs as fast as possible did not reproduce it...

I removed all the Debian patches from unstable's cups (quilt pop -a) and
rebuilt the debs. lpadmin's behaviour was not changed.

An excerpt from a debug2 log for a failure to reinstall a queue is:

  D [12/Mar/2014:18:03:02 +0000] CUPS-Add-Modify-Printer ipp://localhost:631/printers/test-model
  d [12/Mar/2014:18:03:02 +0000] add_printer(0xb821d660[14], ipp://localhost:631/printers/test-model)
  d [12/Mar/2014:18:03:02 +0000] cupsdFindPolicyOp(p=0xb81baac0, op=4003(CUPS-Add-Modify-Printer))
  d [12/Mar/2014:18:03:02 +0000] cupsdFindPolicyOp: Found exact match...
  d [12/Mar/2014:18:03:02 +0000] cupsdIsAuthorized: con->uri="/admin/", con->best=0xb81bc920((null))
  d [12/Mar/2014:18:03:02 +0000] cupsdIsAuthorized: level=CUPSD_AUTH_USER, type=Basic, satisfy=CUPSD_AUTH_SATISFY_ALL, num_names=1
  d [12/Mar/2014:18:03:02 +0000] cupsdIsAuthorized: op=4003(CUPS-Add-Modify-Printer)
  d [12/Mar/2014:18:03:02 +0000] cupsdIsAuthorized: auth=CUPSD_AUTH_ALLOW...
  D [12/Mar/2014:18:03:02 +0000] cupsdIsAuthorized: username="root"
  D [12/Mar/2014:18:03:02 +0000] test-model device-uri: OK
  I [12/Mar/2014:18:03:02 +0000] Setting test-model device-uri to "file:/dev/null" (was "file:/dev/null".)
  d [12/Mar/2014:18:03:02 +0000] set_printer_defaults: device-uri
  d [12/Mar/2014:18:03:02 +0000] copy_file("/var/spool/cups/00000001", "/etc/cups/ppd/test-model.ppd")
  D [12/Mar/2014:18:03:02 +0000] Copied PPD file successfully

ipp.c has:

  /*
   * 'copy_file()' - Copy a PPD file or interface script...
   */

Something seems to think the -P option to lpadmin is being used.

Regards,

Brian.


Reply to: