Issue

• Resuming a print queue by running cupsenable on a queue that is already processing a job (i.e. is not disabled) will cause the next pending job to be started. This can result in multiple connections to a printer and jobs printing out of order.

• After submitting multiple jobs to a print queue that is connected to a slow printer or to a printer that isn't accepting connections, then running "cupsenable <print-queue>" to "resume" the print queue that's already active. For example:

  # lpadmin -p testq -v socket://localhost/ -E
  # lp -d testq /etc/fstab
  request id is testq-1 (1 file(s))
  # lp -d testq /etc/hosts
  request id is testq-2 (1 file(s))
  # lp -d testq /etc/resolv.conf
  request id is testq-3 (1 file(s))
  # cupsenable -d testq
  

  This can cause the print jobs to print out of order.