7 Replies Latest reply: Aug 23, 2012 4:25 PM by bhurte
StevePlumridge Level 1 (0 points)

INstalled the latest driver and can no longer print.  Every app just crashes. 


iMac, OS X Mountain Lion
  • John Blanchard1 Level 5 (5,230 points)

    Assuming this is the same crash seen in several other threads, remove /Library/Printers/hp/PDEs/hpPostScriptPDE.plugin.

     

    If that doesn't help, please post the crash log.

  • StevePlumridge Level 1 (0 points)

    Thanks John.  Saved my bacon!

  • bhurte Level 1 (0 points)

    HP Printer/Scanner Update 2.11 from Software Update/App Store fixed this for me.  It was happening on a Color Laserjet CP1525nw for me after installing 2.10 a few weeks ago - I solved by installing drivers from HP rather than Apple. 2.11 seems to fix the issue.

  • John Blanchard1 Level 5 (5,230 points)

    bhurte wrote:

    I solved by installing drivers from HP rather than Apple.

     

    Apple and HP don't have separate drivers - they're the same.

  • bhurte Level 1 (0 points)

    Nonetheless, installing the drivers downloaded from HP stopped the crashing problem for me that started with the installation of 2.10 from Software Update.  I've installed 2.11 now and don't have the problem.

  • John Blanchard1 Level 5 (5,230 points)

    And you wouldn't have the problem after downloading 2.11 from Apple. The change is from 2.10 to 2.11, not that you downloaded from HP instead of Apple.

  • bhurte Level 1 (0 points)

    The fix for me came initially from installing the HP driver the day 2.10 came out, about 2-3 weeks ago.  I deleted the printer that had updated on 2.10, installed the HP driver, and added the printer back - printing worked again (actually, I deleted and added the printer uner 2.10 too to see if that would solve the crashing - it didn't).  Installing 2.11 today did not reintroduce the problem that 2.10 started.  I deleted the printer that was created under the HP driver before installing 2.11 and added the printer again after 2.11 was installed just to make sure that 2.11 didn't reintroduce the problem that 2.10 introduced.  Sorry if I wasn't clear.