Can't print with canon LBP3250 10.8.2 and CAPT v3.55

That printer is not supported with 10.8

http://support.apple.com/kb/HT3669

For starters, the CAPT v3.55 driver and therefore this printer is supported on 10.8, so ignore the other comment.

The most likely cause for the driver not communicating will be an incorrectly configured print queue. To check how that print queue has been configured, open System Information (Applications > Utilities), select the Printers entry in the left column and then the LBP3250 in the right pane. Information about the printer will be shown, most importantly the print queue URI. Can you please select all the information shown for the LBP3250, and copy and then paste back here so I can check what you have.

Thank you for the information. And no need to apologize for your English. It is much better than my French ;-)

So as you have seen in other posts, the URI is wrong. Yours is showing "usb://Canon/..." while a working CAPT driver has a URI of "cnbma://localhost:59687". The most common cause is the CAPT Backgrounder process not running. So can you confirm by checking Activity Monitor if you can see CAPT Backgrounder.

Thank you for confirming that the CAPT Backgrounder is running.

The next item is the ccpd.conf file. You can open Finder and in the menubar select Go > Go To Folder and type

/Library/Caches/Canon/CUPSCAPT/CCPD

and then press Go. This will open the CCPD folder and here you will see ccpd.conf file. Can you open with TextEdit, select all, copy and paste here what you have.

I would also like to know if this Mac was running 10.6 or 10.7 prior to 10.8 and was the LBP3250 working with the previous OS X?

Thanks for showing me your ccpd.conf file. I can see that it is the older version of the file (the one that came with CAPT v3.40 rather than CAPT v3.55) and more importantly, it is missing an entry to the LPB3250 on the USB port.

Below is an example from my ccpd.conf file for my LBP6300 connected via USB.

#<Printer XXXX>

#DevicePath /dev/usb/lp0

#</Printer>

<Printer Canon_LBP6300>

DevicePath usb://Canon/LBP6300?serial=001E8F2968D0

</Printer>

<Ports>

# socket port

UI_Port 59787

# backend data port

PDATA_Port 59687

</Ports>

You can see that there is the entry about the LBP's connection to the Mac via USB. This is needed because the print queue simply shows a localhost connection to a particular port.

So I suggest the following steps to fix this.

1. Disconnect the LBP3250 USB cable from the Mac

2. Remove the LBP3250 printer from Print & Scan

3. Trash the CUPSCAPT folder in /Library/Printers/Canon

4. Trash the ccpd.conf file in /Library/Caches/Canon/CUPSCAPT/CCPD

5. Restart the Mac and log in.

6. Install the CAPT v3.55 driver

7. Connect the LBP3250 to the Mac and add the printer again.

Now see if you can print. If it still doesn't print, then check the ccpd.conf file again. If it has still failed to create an entry for the LBP3250 then I'm not sure why this would be happening and I will have to do more investigation.

I have a LBP5050N and it has stopped working since I upgraded to 10.8.2 recently, after working since September. It just gets Paused every time I try to print. It still works for Lion with the older driver.

I've read through the other thread here, and basically done what PAHU suggested above, ie,

1. Disconnect the LBP3250 USB cable from the Mac ----- Mine is networked

2. Remove the LBP3250 printer from Print & Scan

3. Trash the CUPSCAPT folder in /Library/Printers/Canon

4. Trash the ccpd.conf file in /Library/Caches/Canon/CUPSCAPT/CCPD

5. Restart the Mac and log in.

6. Install the CAPT v3.55 driver

7. Connect the LBP3250 to the Mac and add the printer again.

There are actually some extra files to trash too, as described in the documentaiton that comes with the driver. In /Library/Printers/PPDs/Contents/Resources, delete CNMC*AUK.ppd.gz. In /Library/LaunchAgents, delete jp.co.canon.CUPSCAPT.BG.plist.

Anyway, after I did all this, the printer worked again. For about half a day - and now it has stopped again. Any time I try to print, I get this in the cups error log:

E [26/Jan/2013:00:17:35 +1100] [Job 131] Can't connect to CCPD: Connection refused

E [26/Jan/2013:00:17:35 +1100] [Job 131] cnbma send_data error, exit

In the system log, the first time it failed this time, I get this:

26/01/13 12:15:46.261 AM PrinterProxy[12166]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

26/01/13 12:15:46.261 AM PrinterProxy[12166]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

I know it is only a warning, but......

The last part of ccpd.conf is:

#<Printer XXXX>

#DevicePath /dev/usb/lp0

#</Printer>

<Printer CanonLBP5050N>

DevicePath net:192.168.200.150

</Printer>

<Ports>

# socket port

UI_Port 59787

# backend data port

PDATA_Port 59687

</Ports>

Any further ideas?

Actually, the Lion machine is using the 3.55 driver too, not the older one. ccpd.conf is exactly the same as on the non-working Mountain Lion.

So it is definitely a Mountain Lion issue, and as everyone is saying, a Mountain Lion 10.8.2 issue.

Is there any way to report this to Canon? It wasn't obvious on their site.....

David Morrison wrote:

Actually, the Lion machine is using the 3.55 driver too, not the older one. ccpd.conf is exactly the same as on the non-working Mountain Lion.

The ccpd.conf file was missing the path to the USB connected printer. Your ccpd.conf file shows the path to the network attached printer, so there is nothing wrong with your ccpd.conf file.

David Morrison wrote:

So it is definitely a Mountain Lion issue, and as everyone is saying, a Mountain Lion 10.8.2 issue.

There is no issue with OS X 10.8.2 and the CAPT v3.55 driver. I have it working on several different Mac's runing 10.8.2.

David Morrison wrote:

Is there any way to report this to Canon?

What's to report? Just because it is working on your 10.7 Mac but not on your Mac running 10.8.2, does not equate to the driver is not compatible with 10.8.2. As I said, I have it working on Mac's running a clean build of 10.8.2 and it is working fine. And if you did report your assumption, then Canon would also test on a clean install of 10.8.2 and find it also works.

What you would have to report is that it is not working on your Mac, although your reinstallation of the CAPT driver shows that it did work for a while on 10.8.2 but that you have some other conflict with the driver on your Mac.

BTW - I did reply to your other post where you said it would sometimes fail to print all pages. But here you have said it does not print at all. So is the cups error log you show above appearing every time you try to print now? If yes, then it reads like the printing system is having trouble with accessing the Canon CAPT files. Try opening Disk Utility and running a repair disk permissions.

PAHU wrote:

So it is definitely a Mountain Lion issue, and as everyone is saying, a Mountain Lion 10.8.2 issue.

There is no issue with OS X 10.8.2 and the CAPT v3.55 driver. I have it working on several different Mac's runing 10.8.2.

Firstly, there is obviously a problem because a fair number of people are complaining it stopped working as soon as they updated to 10.8.2, with no other changes to their computers. Just because yours is working does not mean that there is not a problem, just that you do not have the conditions that expose it.

Secondly, the problem may not be in 10.8.2 as such. 10.8.2 may have changed something enough to cause a conflict between the printer driver and something else that the people suffering the problem have installed.

Thirdly, if there is a conflict of some kind, then Canon needs to know about it so they and the author of the other item can work together, possibly with Apple, to resolve it.

BTW - I did reply to your other post where you said it would sometimes fail to print all pages. But here you have said it does not print at all. So is the cups error log you show above appearing every time you try to print now? If yes, then it reads like the printing system is having trouble with accessing the Canon CAPT files. Try opening Disk Utility and running a repair disk permissions.

I said in the other item that it had been forgetting to print the last few pages for *several years*, which of course predates 10.8.2 by a long time. It also happens on several different Macs and on Leopard to Mountain Lion. More in the other thread.

In this instance, I tried repairing disk permissions - thank you for the reminder - but it made no difference to the printer working. What did make a difference was rebooting into Safe Mode, and repairing the permissions then. After I rebooted, the printer has been working again. It may have been merely rebooting into Safe Mode that fixed the problem (it often does for all sorts of problems), or it may have been the repaired permissions done in Safe Mode. However, I have not printed much since then, so I do not know if this is a permanent fix.

David Morrison wrote:

Just because yours is working does not mean that there is not a problem, just that you do not have the conditions that expose it.

Exactly. I have no issue with the driver on 10.8.2 because I don't have the conditions that expose it. And a clean installation of 10.8.2 also does not have the conditions that expose it so the driver works fine.

David Morrison wrote:

Secondly, the problem may not be in 10.8.2 as such. 10.8.2 may have changed something enough to cause a conflict between the printer driver and something else that the people suffering the problem have installed.

And this is my point. You cannot say that this driver is not compatible with 10.8.2. But you can say what you have said here and that is your Mac, and others experiencing problems after upgrading to 10.8.2, has some other application or utility installed (or had installed) that has only created this issue since the update.

David Morrison wrote:

Thirdly, if there is a conflict of some kind, then Canon needs to know about it so they and the author of the other item can work together, possibly with Apple, to resolve it.

True again. But what other item do you have that is causing the problem? Canon does not have your setup. They will have a clean installation of 10.8.2. So how do they determine the cause? Do they have to obtain/purchase every application and utility you have? Would you be prepared to give them a clone of your Mac so they can test?

By all means report that you are having problems with your local Canon support. But if you tell them that the driver is not compatible with 10.8.2 they are going to tell you that it is.

PAHU wrote:

Secondly, the problem may not be in 10.8.2 as such. 10.8.2 may have changed something enough to cause a conflict between the printer driver and something else that the people suffering the problem have installed.

And this is my point. You cannot say that this driver is not compatible with 10.8.2. But you can say what you have said here and that is your Mac, and others experiencing problems after upgrading to 10.8.2, has some other application or utility installed (or had installed) that has only created this issue since the update.

If you read what I have written, you will see I do not say anywhere that it is incompatible. You are the only one who has used that word, and you have used it repeatedly to deny there is a problem.

PAHU wrote:

True again. But what other item do you have that is causing the problem? Canon does not have your setup. They will have a clean installation of 10.8.2. So how do they determine the cause? Do they have to obtain/purchase every application and utility you have? Would you be prepared to give them a clone of your Mac so they can test?

The cause has yet to be determined, but while you keep denying there is a problem, we will never find out. How about making some suggestions as to how to determine what the issue is?

And as for Canon support, the only time I did ever contact them they were unhelpful in the extreme, denying there was a problem when there clearly was. Hmmm... that's remarkably similar to the discussion here......

Just out of curiosity, are you a Canon employee?