How to remove jobs from the print queue in Linux

Written by stephen byron cooper Google
  • Share
  • Tweet
  • Share
  • Pin
  • Email
How to remove jobs from the print queue in Linux
Linux has a Unix-like command set. (Linux)

Linux is a Unix-like operating system that works at the command line. There are Windows-based user interface options for computers running Linux, principally the Ubuntu interface. The command line, however, is the home to traditional Linux utilities like the print manager commands. In order to cancel a print job from the print queue you first need to list the jobs in the queue to find out the job number of the print you want to cancel.

Skill level:

Other People Are Reading


  1. 1

    Go to the command line of Linux if you have a print end sitting on top of it. It does not matter which directory of the file structure you are in because the printer commands are universal.

  2. 2

    Get a listing of the current jobs in the printer queue. Enter “lpq” (without the quotes) and hit the “Enter” key. You will be shown a list of jobs currently queuing to be printed.

  3. 3

    Look for the file name of the print out you want to cancel in the “Files” column or the lpq output. Read back to the previous column in that row. That column represents the job number. You need to note down this job number in order to cancel the print.

  4. 4

    Issue the command “lprm XX” but put the job n umber of the print you want to cancel instead of “XX.” Press the “Enter” key. The specified print job will be removed from the print queue.

Tips and warnings

  • If you are too slow and the print job has already entered the printer before you issue the lprm command you can remove the print job from the printer’s memory by turning it off and on again.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.