You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Installed Yosemite, printing stops working on my Canon iSensys LBP5360 (aka Canon Color Imagerunner outside Europe).
The print queue says "Stopped - 'filter' failed".
Worked fine yesterday on Mavericks.
Any ideas? Be gentle - I moved from Windows after 29 years last July...
Bill.
MacBook Pro with Retina display, OS X Yosemite (10.10)
Been driving me crazy trying to figure out why my Mac Pro, and MacBook Pro suddenly couldn't print (to my Epson WorkForce 635) after installing Yosemite. Tried everything to get rid of the "Stop - 'Filter' failed" message. Did the whole "search the internet" thing for a solution, and finally bit the bullet and contacted Epson directly. Their response (which worked BTW) was:
And it did the trick on both of my machines. I suspect deleting the resources and cache had a lot to do with it.
Your mileage may vary.
JM
Update: I've found a couple of workarounds, which I note here for others - not really solutions as such.
Firstly, using the Generic PCL driver results in a poor quality, black and white only print.
Secondly, and more usefully, I've used one of my Windows PCs which has the printer installed to share this device locally, and then connected the Mac to this 'Windows' printer (even though it's still just an IP network printer) specifying the same Canon LBP5360 driver on the Mac. Curiously, everything works fine if channelled via Windows 7 - full colour and quality.
Weird.
And it sort of defeats the point of having a network printer, but what the heck, at least I can print, even if I do have to carry on swearing about Windows every time I look at it.
The console reports the following for a single print attempt. Even as a (former, aging) Java developer, this is pretty meaningless to me, though it does look like perhaps the firewall blocked the outbound request (deny network-outbound)?
The printer is at 192.168.1.39, by the way.
Bill.
17/10/2014 18:29:41.297 lsregister[3032]: LaunchServices: Begin database seeding
17/10/2014 18:29:41.297 lsregister[3032]: LaunchServices: Completed database seeding
17/10/2014 18:29:41.297 lsregister[3033]: LaunchServices: Begin database seeding
17/10/2014 18:29:41.298 lsregister[3033]: LaunchServices: Completed database seeding
17/10/2014 18:29:51.936 iSensys_LBP5360[3042]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
17/10/2014 18:29:51.936 iSensys_LBP5360[3042]: 0 CarbonCore 0x00007fff8b172dc3 ___Gestalt_SystemVersion_block_invoke + 113
17/10/2014 18:29:51.936 iSensys_LBP5360[3042]: 1 libdispatch.dylib 0x00007fff94976c13 _dispatch_client_callout + 8
17/10/2014 18:29:51.936 iSensys_LBP5360[3042]: 2 libdispatch.dylib 0x00007fff94976b26 dispatch_once_f + 117
17/10/2014 18:29:51.936 iSensys_LBP5360[3042]: 3 CarbonCore 0x00007fff8b11b4da _Gestalt_SystemVersion + 987
17/10/2014 18:29:51.936 iSensys_LBP5360[3042]: 4 CarbonCore 0x00007fff8b11b0c7 Gestalt + 144
17/10/2014 18:29:51.936 iSensys_LBP5360[3042]: 5 xdclfilter 0x0000000100012e9a createCommonData + 14981
17/10/2014 18:29:51.936 iSensys_LBP5360[3042]: 6 xdclfilter 0x000000010000c067 main + 546
17/10/2014 18:29:51.966 sandboxd[252]: ([3042]) xdclfilter(3042) deny network-outbound 192.168.1.39:47545
17/10/2014 18:29:52.177 sandboxd[252]: ([1695]) storeuid(1695) deny mach-lookup com.apple.dock.server
17/10/2014 18:29:54.705 com.apple.xpc.launchd[1]: (com.apple.quicklook[3045]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
17/10/2014 18:30:00.694 sandboxd[252]: ([1695]) storeuid(1695) deny mach-lookup com.apple.dock.server
The end of the error log associated with the console output shown in my other post is as follows:
D [17/Oct/2014:18:29:51 +0100] [Job 5] Started filter /usr/libexec/cups/filter/pstoappleps (PID 3036)
D [17/Oct/2014:18:29:51 +0100] [Job 5] Started filter /usr/libexec/cups/filter/pstopdffilter (PID 3037)
D [17/Oct/2014:18:29:51 +0100] [Job 5] Started filter /Library/Printers/Canon/CUPS_Printer/Bins/capdftopdl (PID 3038)
D [17/Oct/2014:18:29:51 +0100] [Job 5] Started backend /usr/libexec/cups/backend/lpd (PID 3039)
D [17/Oct/2014:18:29:51 +0100] [Job 5] capdftopdl start.
D [17/Oct/2014:18:29:51 +0100] [Job 5] Writing PageSize code width = 595.000000, height = 842.000000
D [17/Oct/2014:18:29:51 +0100] [Job 5] STATE: +connecting-to-device
D [17/Oct/2014:18:29:51 +0100] [Job 5] Looking up "192.168.1.39"...
D [17/Oct/2014:18:29:51 +0100] [Job 5] backendWaitLoop(snmp_fd=5, addr=0x7fda617003d8, side_cb=0x10f344abb)
D [17/Oct/2014:18:29:51 +0100] [Job 5] PID 3036 (/usr/libexec/cups/filter/pstoappleps) exited with no errors.
D [17/Oct/2014:18:29:51 +0100] [Job 5] PID 3037 (/usr/libexec/cups/filter/pstopdffilter) exited with no errors.
D [17/Oct/2014:18:29:51 +0100] [Job 5] STATE: -com.canon.unsupportedsize-error
D [17/Oct/2014:18:29:51 +0100] [Job 5] PID 3039 (/usr/libexec/cups/backend/lpd) exited with no errors.
D [17/Oct/2014:18:29:51 +0100] [Job 5] PID 3038 (/Library/Printers/Canon/CUPS_Printer/Bins/capdftopdl) stopped with status 1.
D [17/Oct/2014:18:29:51 +0100] [Job 5] Hint: Try setting the LogLevel to "debug" to find out more.
D [17/Oct/2014:18:29:51 +0100] [Job 5] End of messages
D [17/Oct/2014:18:29:51 +0100] [Job 5] printer-state=3(idle)
D [17/Oct/2014:18:29:51 +0100] [Job 5] printer-state-message="Filter failed"
D [17/Oct/2014:18:29:51 +0100] [Job 5] printer-state-reasons=none
E [17/Oct/2014:18:33:29 +0100] [Job 4] Stopping unresponsive job.
E [17/Oct/2014:18:34:52 +0100] [Job 5] Stopping unresponsive job.
Printing from Pages results in a slightly different Console output - not sure this is any more helpful, but I'll post it anyway... the comment about the Gestalt selector version being 10.9 looks suspicious to me, but what do I know!
Bill.
17/10/2014 18:50:22.182 Pages[3179]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
17/10/2014 18:50:22.182 Pages[3179]: 0 CarbonCore 0x00007fff8b172dc3 ___Gestalt_SystemVersion_block_invoke + 113
17/10/2014 18:50:22.182 Pages[3179]: 1 libdispatch.dylib 0x00007fff94976c13 _dispatch_client_callout + 8
17/10/2014 18:50:22.183 Pages[3179]: 2 libdispatch.dylib 0x00007fff94976b26 dispatch_once_f + 117
17/10/2014 18:50:22.183 Pages[3179]: 3 CarbonCore 0x00007fff8b11b4da _Gestalt_SystemVersion + 987
17/10/2014 18:50:22.183 Pages[3179]: 4 CarbonCore 0x00007fff8b11b0c7 Gestalt + 144
17/10/2014 18:50:22.183 Pages[3179]: 5 CUPSUFR2PDECommon 0x000000011582ed89 -[CUPSUFR2PdeController initWithCallback:bundle:funcList:] + 181
17/10/2014 18:50:22.183 Pages[3179]: 6 CUPSUFR2PDECommon 0x000000011582bd25 -[CUPSUFR2PDEPanelCommon initWithCallback:bundle:funcList:] + 49
17/10/2014 18:50:25.639 iSensys_LBP5360[3197]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
17/10/2014 18:50:25.639 iSensys_LBP5360[3197]: 0 CarbonCore 0x00007fff8b172dc3 ___Gestalt_SystemVersion_block_invoke + 113
17/10/2014 18:50:25.639 iSensys_LBP5360[3197]: 1 libdispatch.dylib 0x00007fff94976c13 _dispatch_client_callout + 8
17/10/2014 18:50:25.639 iSensys_LBP5360[3197]: 2 libdispatch.dylib 0x00007fff94976b26 dispatch_once_f + 117
17/10/2014 18:50:25.639 iSensys_LBP5360[3197]: 3 CarbonCore 0x00007fff8b11b4da _Gestalt_SystemVersion + 987
17/10/2014 18:50:25.639 iSensys_LBP5360[3197]: 4 CarbonCore 0x00007fff8b11b0c7 Gestalt + 144
17/10/2014 18:50:25.639 iSensys_LBP5360[3197]: 5 xdclfilter 0x0000000100012e9a createCommonData + 14981
17/10/2014 18:50:25.639 iSensys_LBP5360[3197]: 6 xdclfilter 0x000000010000c067 main + 546
17/10/2014 18:50:25.668 sandboxd[252]: ([3197]) xdclfilter(3197) deny network-outbound 192.168.1.39:47545
Thank you very much for posting the logs. The Gestalt messages are warnings, but misleading. The
17/10/2014 18:29:51.966 sandboxd[252]: ([3042]) xdclfilter(3042) deny network-outbound 192.168.1.39:47545
is the sandbox "violation" that is causing the driver to fail. Canon will have to fix their drivers.
My pleasure, Bill. Maybe adding the printer with the Generic PostScript (or PCL?) ppd will get you printing in the meantime. If so, you'll have limited functionality, but it might be better than nothing.
It's hard to say, John - you go onto the Canon site, and select the device, and it just says "you don't need a driver" which is nonsense of course. I'm not entirely sure how all this works in OS X - on Windows, you always have to install an explicit driver, but I've assumed from messages like that that the Mac somehow downloads the right one and keeps it up to date. I'm not even sure whether Apple writes these or Canon does.
Just double checked. The USA and Australian Canon sites just list nothing once they auto detect Yosemite... The latest Canon driver they list on the UK support site is March 2014. Downloaded the PKG and tried to install it, and it won't install, saying it's for a previous OS version.
I've had this type of issue before - USA has drivers that work, EMEA don't, that sort of nonsense.
So as you said earlier, I guess we will just have to wait for Canon to get their act together.
Thank you again, Bill. Canon writes the drivers, and Apple facilitates the delivery process with Software Update. I think that's what they mean when they say you don't need a driver, that it is available through Software Update, and then Software Update is responsible for keeping it current. If Software Update doesn't list anything available, you're most likely current.
If I use the driver which worked until I installed Yosemite I get the "filter failed" message. On the console I see
OKIHC004(1881) deny network-outbound 192.168.0.2:9100
I tried with Generic PCL driver, it seems ok, but printer reports "invalid data". I use OKI C3530 printer.
Any ideas?
The only workaround I've found so far is to use a windows computer as a print server. So I've set up a windows PC with the correct windows driver, then shared it on the network, then set Yosemite to use this printer, specifying the earlier Mavericks print driver as the one to use. It's an ugly solution, but it worked for me, always assuming you have a PC lying around the place. Best I can suggest - sorry.
Hi Bill, I have the same problem, so rest assured your not alone. I fixed mine. I'd like to share with you my fix and perhaps you might get back online.
This happened in error but it worked none the less, I reset my printing system via system prefs (this wipes your computer of all printers, regardless if they work or not! tread carefully)
No I had no printers installed, no loss right? It wasn't working on my Canon i5235iR network laser.
I then went to add a new printer, selected IP as the method, in the top address I put, the dns addy of my printer, in my case its 192.168.0.xx, then it searched and offered me a generic printer driver, I then chose to select the driver and in the search I put in my printer name and found the Mavericks driver , selected it and I was back online on the mavericks driver, all good.
Hope this helps.
Hi SpaceDesign911 - actually, I already tried exactly those steps last week, and it didn't work. Reset the print system, specified the IP address, selected the Mavericks driver. No deal. Clearly some difference, either in the drivers or the way you went about it compared to me. Did you restart the machine during this process?
Thanks Paulo! Now, if I can just figure out how to print your instructions ... 😕
By the way, there was a post from iKokie which specified how to switch off the sandboxing to make this work. These posts have been deleted, presumably by Apple, but they didn't specify why which is pretty annoying. I suppose they don't like their new security being compromised, and obviously we are not adult enough to decide for ourselves (I'm 52, btw, and been coding since I was 18...)
printing - 'filter failed'
