Skip navigation

Updated to 10.6.8, now I can't print

186001 Views 376 Replies Latest reply: Feb 21, 2014 2:25 PM by ETeague RSS
  • PAHU Level 6 Level 6 (14,400 points)
    Currently Being Moderated
    Jun 25, 2011 4:11 AM (in response to jstottmarketing)

    Thank you James Stott for posting the cups error log. It is showing that the dnssd service (Bonjour) is crashing. It is also showing that you are using a Fiery (based on the lpd protocol using the print queue name).

     

    If Bonjour is failing due to permission errors, then as MacBerto has mentioned, using Disk Utility to repair disk permissions may help. Also, downloading and installing the 10.6.8 Combo update may resolve the problem - this has been a known action to resolve printing issues after point updates since 10.4.

     

    It would also be nice to know what permissions the dnssd and lpd services are currently set to prior to the repairing the permissions. Looking at my Mac, the permissions have not changed from 10.6.7 to 10.6.8. Both services have their permissions to 700, while socket is set to 555, so Linc Davis' suggestion to change the permissions to 755 may work but I feel it is not needed.

     

    Also, the suggestions in this thread to replace the new version of backend files, such as socket, with the version included with 10.6.7 may succeed due to the action simply changing the permissions on the files.

     

    So to check the permissions you can open Terminal and change from the logged in user location to the backend folder by typing

     

    cd /usr/libexec/cups/backend

     

    and pressing ENTER. Then type

     

    ls -al

     

    and pressing ENTER. This will display all the contents of the files within the backend folder and the permissions set on the files. For dnssd and lpd, I would expect the failing Mac's to show something other than

     

    -rwx------ (that's 6 dashes after rwx)

     

    and socket to be something other than

     

    -r-xr-xr-x

  • Alejandro F. B. Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jun 25, 2011 6:37 AM (in response to PAHU)

    Thanks Pahu, I tried printing to a HP LaserJet 1022 (USB) and an HP LaserJet 4600 (networked) and printed Ok in both cases. But even after following your suggestions (fixing permissions) I am still unable to print wireless to my Epson NX420. I also reinstalled the 10.6.8 upgrade as MacBerto suggested but still no solution in sight. I spoke with an Apple representative and they sent me a Capture Data app and asked me to send them the results to pass the issue to the engineers.

  • Alejandro F. B. Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jun 25, 2011 8:14 AM (in response to PAHU)

    Thanks PahuL

     

     

    For dnssd and lpd, I would expect the failing Mac's to show something other than

     

    -rwx------ (that's 6 dashes after rwx)

     

    and socket to be something other than

     

    -r-xr-xr-x

     

     

    I checked, and my permissions are the same as the ones you listed, But still I cannot print wireless ....

  • JohnnyM28 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jun 25, 2011 8:26 AM (in response to Alejandro F. B.)

    My permissions are as listed above, however I still can't print.

  • Csound1 Level 7 Level 7 (32,245 points)
    Currently Being Moderated
    Jun 25, 2011 8:35 AM (in response to headyfrombrigantine)

    headyfrombrigantine wrote:

     

    Thanks Apple,

    Ever thought about testing your f*%@@#ing software before you push it out the factory and onto us poor saps?

    I "try" to make money using your hardware - but if I can't print then I can't make money.

    You don't know how ****** I am.

     

    ******' jokers.

     

    It appears that the update has also corrupted your keyboard.

  • Pedaler Level 1 Level 1 (5 points)
    Currently Being Moderated
    Jun 25, 2011 9:01 AM (in response to PAHU)

    Here's what Terminal shows for permissions. iMac is running 10.6.8.

    Note that I grabbed a copy of 'socket' from another Mac (G4 Sawtooth) running 10.6.7.

    'socket' was copied in from 10.6.7; 'socket copy' was copy of original messed up file after the 10.6.8 update.

     

    -r-xr-xr-x@  1 root  wheel    75200 Jan  4 00:22 socket

    -r-xr-xr-x   1 root  wheel    79328 Apr 29 17:45 socket copy

     

    I don't get into Terminal too often, so I appreciate the patient and helpful comments by all in this thread! It's encouraging to know there are still folks out there who want to share what they know, and are willing to help others without expecting a red carpet and trophy.

  • Matt Broughton Level 5 Level 5 (4,905 points)
    Currently Being Moderated
    Jun 25, 2011 9:04 AM (in response to Linc Davis)

    Linc Davis wrote:

     

    This is a possible fix for the printing issue.

    ...

    Launch the Terminal application and copy or drag -- DO NOT TYPE -- the following text into the window:

     

    sudo chmod 755 /usr/libexec/cups/backend/*

     

    Sorry to say, I think this would be a waste of time.  Did you compare the permissions that worked on 10.6.7 and what appeared after installing 10.6.8?  They are the same.  Some selected examples based on the backends people are having problems with here:

     

    10.6.7

    -rwx------  1 root  wheel    57344 Mar 29 12:19 dnssd

    -rwx------  1 root  wheel   106096 Mar 29 12:19 ipp

    -rwx------  1 root  wheel    93024 Mar 29 12:19 lpd

    -r-xr-xr-x  1 root  wheel    75200 Mar 29 12:19 socket

    -r-xr-xr-x  1 root  wheel    91792 Mar 29 12:19 usb

     

    10.6.8

    -rwx------  1 root  wheel    57344 Apr 29 17:45 dnssd

    -rwx------  1 root  wheel   106096 Apr 29 17:45 ipp

    -rwx------  1 root  wheel    93024 Apr 29 17:45 lpd

    -r-xr-xr-x  1 root  wheel    79328 Apr 29 17:45 socket

    -r-xr-xr-x  1 root  wheel    91792 Apr 29 17:45 usb

     

    I don't have the answer to the problem, but I don't want to send people to the Terminal and have them use any type of sudo command unless there is some basis that the command will solve their problem.

  • Linc Davis Level 10 Level 10 (107,375 points)
    Currently Being Moderated
    Jun 25, 2011 9:17 AM (in response to Matt Broughton)

    I don't want to send people to the Terminal and have them use any type of sudo command unless there is some basis that the command will solve their problem.

     

    The basis is that it worked for me.

  • Ziatron Level 4 Level 4 (3,255 points)
    Currently Being Moderated
    Jun 25, 2011 9:27 AM (in response to rafavalles)
    Does any one know if is possible to Downgrade ??

     

    It's easy, I used Time Machine to go back to 10.6.7.  Took 2 minutes.

     

    All printers working perfectly now.

  • Matt Broughton Level 5 Level 5 (4,905 points)
    Currently Being Moderated
    Jun 25, 2011 9:27 AM (in response to Linc Davis)

    Linc Davis wrote:

     

    I don't want to send people to the Terminal and have them use any type of sudo command unless there is some basis that the command will solve their problem.

     

    The basis is that it worked for me.

    I can't argue with that even if I can't explain the reason it worked.

  • dnaritoku Calculating status...
    Currently Being Moderated
    Jun 25, 2011 9:49 AM (in response to velocius)

    Thanks, your solution worked like a charm. Also thanks for also sharing the 10.6.7 socket file, very necessary.

  • tim-dk Calculating status...
    Currently Being Moderated
    Jun 25, 2011 10:36 AM (in response to mac-col)

    Disconnect the printer from your computer either by switching it off or remove the ethernet cable. Postpone all waiting printing jobs form the printer menu, enable printing, repeat printing. After this the printer driver starts to connect to the printer. Now you switch on or connect the printer again, and it should start printing - hopefully. My Xanté CL30 printer did so.

     

    You have to do this every time you want to print, so it is not a permanent solution only a work around until Apple release a patch for 10.6.8

  • skylab55 Calculating status...
    Currently Being Moderated
    Jun 25, 2011 11:17 AM (in response to tim-dk)

    I could not print either til I unplugged the network printer as described above, and then plug back in and the print job worked. all my networked printed this way, I have 4 of them, hopefully Apple comes out with a fix.

  • srca Calculating status...
    Currently Being Moderated
    Jun 25, 2011 2:06 PM (in response to sp0radic)

    The solution posted by velocius does work but your specific situation may require a file other than the socket file. The error that velocius had was: "/usr/libexec/cups/backend/socket failed". If that is the exact message you have then replace the socket file. I had "usr/libexec/cups/backend/lpd failed". I replaced the lpd file and my printing now works.

  • dhelmy Level 1 Level 1 (20 points)
    Currently Being Moderated
    Jun 25, 2011 6:14 PM (in response to srca)

    Thank you for your suggestion. I replaced the file /usr/libexec/cups/backend/lpd with the one from another laptop that has not been upgraded and now the printing works.

1 ... 6 7 8 9 10 ... 26 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (14)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.