HP Colour Laserjet 1515N printing paused

Hi all,

I have a HP Colour Laserjet 1515N, which has just started acting up.

Every time I try to send a job to the printer, I get the printer's icon with a pause symbol appear in my dock and when I click on the print job, followed by the info icon, I get the message in the screenshot here
What I've tried so far, without success:
Deleting and re-adding the printer via System preferences ->Print & Fax
Resetting the printer to defaults
Printing from another user's account

What I can do:
Ping the printer from terminal
Access the printer's on-board web config pages

I'm at a loss as what to try next - Any help would be greatly appreciated.

Thanks in advance.

I had strikingly similar symptoms (could ping and web into, but machine could not detect) after the 10.6.8 update - but rather unhelpfully, a simple restart of the printer got things going again.

I suspect 6.8 might have bust a couple of HP drivers.

In reply to a post by ian_c:

I had strikingly similar symptoms (could ping and web into, but machine could not detect) after the 10.6.8 update - but rather unhelpfully, a simple restart of the printer got things going again.

I suspect 6.8 might have bust a couple of HP drivers.

Hi ian,

Thanks for your prompt reply. I think you could be onto something, there as the printer was working nicely, up until recently but TBH this is the first time I've needed to print in about 2 weeks.

Have you updated to 10.6.8 by any chance? A lot of users seem to be reporting this problem after the update. Google "dnssd failed 10.6.8" and you'll get a number of hits. This thread offers a solution which may be worth trying. Or you could wait for Apple to offer an update to the affected file, but that could take a while.

Quite a few reports if you google "/usr/libexec/cups/backend/dnssd failed".

Have you tried the usual Verify Disk / Repair Permissions?

Tbh I've never had it cure anything yet, but there's always a first time!


edit- never mind, others beat me to it with more useful replies

Edited by billford (Tue 28-Jun-11 21:27:00)

In reply to a post by billford:

Have you tried the usual Verify Disk / Repair Permissions?

Tbh I've never had it cure anything yet, but there's always a first time!

Hi Bill,

Yep, I've repaired permissions - one of the first things that I tried. And yes, you're right - it helped as much as a choccy fire guard! lol

Thanks for the suggestion, though.

In reply to a post by AEP:

Have you updated to 10.6.8 by any chance? A lot of users seem to be reporting this problem after the update. Google "dnssd failed 10.6.8" and you'll get a number of hits. This thread offers a solution which may be worth trying. Or you could wait for Apple to offer an update to the affected file, but that could take a while.

Hi AEP,

Yes I did the update to 6.8 (I try to keep my system updated as much as possible).
Thanks for the link to that other thread - I'll go and digest it now.

By the way, is there any way that we, as mere users can send Apple a bug report, in the vain hope that they'll sort this out sooner rather than later?

In reply to a post by john2007:

Quite a few reports if you google "/usr/libexec/cups/backend/dnssd failed".

Hi John,

Thanks for taking the time to reply - It is appreciated.
Unfortunately, I didn't identify those exact key words when I chatted to Mr. Google earlier, but I will do so now.

Here's an article listing the various ways you can get feedback to Apple. How effective the different methods are, I don't know. I suspect a pukka bug report would be best, but I think you need to be in their Developer Program to do that (but it is free).

Useful link that, bookmarked.

Thanks.

Try another USB cable? the pause often indicates it isn't connected.

I believe that's a networked printer.

In reply to a post by gilesjuk:

Try another USB cable? the pause often indicates it isn't connected.

Hi giles,

The printer's networked and I have already tried another cable as part of my troubleshooting process.

Thanks for the suggestion - It is appreciated.

In reply to a post by AEP:

Here's an article listing the various ways you can get feedback to Apple. How effective the different methods are, I don't know. I suspect a pukka bug report would be best, but I think you need to be in their Developer Program to do that (but it is free).

Hi again AEP.

Thanks for that link - It's appreciated.

I did a little googling and found this link for Apple's online feedback form, but surprisingly enough, the most recent version of OS X they have listed is .6.7

Here's a nice clear explanation of how to patch it. But also report as bug to Apple - the more they get the quicker it will be sorted.

http://reviews.cnet.com/8301-13727_7-20074767-263/ho...

In reply to a post by ian_c:

Here's a nice clear explanation of how to patch it. But also report as bug to Apple - the more they get the quicker it will be sorted.

http://reviews.cnet.com/8301-13727_7-20074767-263/ho...

Hi again ian,

Many thanks for that. Unfortunately, though I don't have a TM backup right now, as my TM drive died about 6 weeks ago. Oh well, I guess I'll have to manually backup and do a clean reinstall, then update as far as .6.7 with the combo updater.

Yikes. Bummer on the TM. Always when you need it...

In reply to a post by ian_c:

Yikes. Bummer on the TM. Always when you need it...

Yep, just my luck! If only I could find someone who has the 10.6.7 version of the dnssd file and is willing to host it, then I might stand a chance of avoiding a clean reinstall.

Edited cos I'm tired and got the file name wrong

Edited by Basenji (Tue 28-Jun-11 23:25:32)

hang on...

*cough* http://www.2shared.com/file/8JHgr-nK/socket.html

(courtesy of the Applel thread linked above)

Edited by ian_c (Tue 28-Jun-11 23:51:50)

In reply to a post by ian_c:

hang on...

*cough* http://www.2shared.com/file/8JHgr-nK/socket.html

(courtesy of the Applel thread linked above)

Thanks for that, Ian - I have been reading that thread diligently.

It appears that some people are having to replace four files from the /backend folder: socket, dnssd, ipp and lpd in order to get their printers working.

On a slight side note, I had the bright idea of adding the printer via IP address and attempting to print via HP Directjet, but got a similar error message, stating this time that the lpd file had crashed.

I think I'll just do a manual backup and clean install from scratch - Seems the most hastle-free way of getting up-and-running once more.

Ah, gotcha

Sadly I've updated and seem to be working, touch wood, or I would sort them out for you.

In reply to a post by ian_c:

Ah, gotcha

Sadly I've updated and seem to be working, touch wood, or I would sort them out for you.

Me again! lol

I finally got it sorted. Some kind soul hosted a file that changed the permissions on the 4 files I mentioned. Thanks once again for pointing me in the direction of that thread.(The solution above was buried on page 10 of that thread).

Here's a link to the file mentioned http://www.geocities.jp/horiemonmail/Repair10.6.8.dmg

Ran that file and punched in my admin PW now everything is working as it should.

Thanks to everyone who contributed.

Edited by Basenji (Wed 29-Jun-11 00:26:44)

In reply to a post by Basenji:

I finally got it sorted. Some kind soul hosted a file that changed the permissions on the 4 files I mentioned.

Glad you got it working

Suggestion- a stickie on your desktop, in 36-point bold red:

DO NOT REPAIR PERMISSIONS!

In reply to a post by billford:

In reply to a post by Basenji:

I finally got it sorted. Some kind soul hosted a file that changed the permissions on the 4 files I mentioned.

Glad you got it working

Suggestion- a stickie on your desktop, in 36-point bold red:

DO NOT REPAIR PERMISSIONS!

Now are you sure that 36pt will be big enough, Bill? I was thinking more like 144pt
Seriously, though I think tomorrow I'll head off down to (urgh!) PCW to get another TM disk (I kinda "need" a new 21.5 monitor too and there's an AOC one they have for £129.99 that's been calling my name each time I walk past, so I guess I'll have to do the right thing and give it a loving home! )

Even so, ethernet cables go bad

I would definitely recommend that you don't "Try another USB cable" to replace a bad ethernet cable.

Tbh I've never had it cure anything yet

For you and lots and lots of people. I think Mac users repairing permissions has about as much effect for the vast majority of Mac users as St Genarro's blood supposedly liquifying has on the good fortune of the population of Naples.

Supplemental release to 10.6.8 addresses this and a couple of other bits and bobs.

In reply to a post by ian_c:

Supplemental release to 10.6.8 addresses this and a couple of other bits and bobs.

Thanks for the heads-up, Ian Greatly appreciated.