Can't print with PostScript driver for HP LaserJet 1200

Asked by Stefan Nagy

In Debian Wheezy, if I connect the HP LaserJet 1200, the printer get's installed automatically with the PostScript driver (PPD), which doesn't work.

There are two different Postscript PPDs: foomatic and the other one is, I guess, included in the hplip packages. So as far as I understand it, the HPLIP Postscript driver seems to be the default driver, which is installed automatically.

This question is not about me having problems with printing (all the other PPDs are working, hpijs gives me the best results) – the problem is, that the default driver doesn't work (which is a problem for less experienced users).

When I try to print a CUPS test page, the LED blinks green (which means something like 'receiving data') for 23 minutes (!), after that the LaserJet prints 2 pages: the first is empty, the second contains the following error message:


Please tell me if you need more information.

Question information

English Edit question
HPLIP Edit question
No assignee Edit question
Solved by:
Stefan Nagy
Last query:
Last reply:
Revision history for this message
Stefan Nagy (stefan-nagy) said :

Sorry, HPLIP version is 3.12.6. And I also forgot to mention that the Foomatic/PostScript driver won't work either (just for your information – I know that it's not part of HPLIP).

Revision history for this message
Sanjay Kumar (sanjay-kumar14) said :


Thanks for reporting the issue in HPLIP. Please follow following things.
=> Download and install the latest HPLIP release from (automatic installer) or (manual installation, if automatic installer does not work)

=> Reconfigure print queue with the commands in the terminal mentioned below.
       => system-config-printer (remove all print queues)
      => su -c "hp-plugin"
      => sudo hp-plugin (This will download right plugin)
       => hp-setup (It should not be run in a root mode. This command is adding print queue, make sure you select ppd name having "-ps" or "hpcups" substring)
=>Try printing now.

Revision history for this message
Stefan Nagy (stefan-nagy) said :

Seems like the problem is related to the CUPS USB backend, not the two mentioned PPDs.

For more information see