BillBrook

Q: printing - 'filter failed'

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)

Posted on Oct 17, 2014 5:26 AM

Close

Q: printing - 'filter failed'

  • All replies
  • Helpful answers

Page 1 of 3 last Next
  • by BillBrook,

    BillBrook BillBrook Oct 17, 2014 8:10 AM in response to BillBrook
    Level 1 (0 points)
    Oct 17, 2014 8:10 AM in response to BillBrook

    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.

  • by John Blanchard1,

    John Blanchard1 John Blanchard1 Oct 17, 2014 9:09 AM in response to BillBrook
    Level 5 (5,243 points)
    Oct 17, 2014 9:09 AM in response to BillBrook

    Do you see anything in /Utilities/Console indicating which filter failed? Or anything in /var/logs/cups/error_log that mentions the filter failure or anything related to sandbox?

  • by BillBrook,

    BillBrook BillBrook Oct 17, 2014 10:34 AM in response to John Blanchard1
    Level 1 (0 points)
    Oct 17, 2014 10:34 AM in response to John Blanchard1

    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

  • by BillBrook,

    BillBrook BillBrook Oct 17, 2014 10:43 AM in response to John Blanchard1
    Level 1 (0 points)
    Oct 17, 2014 10:43 AM in response to John Blanchard1

    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.

  • by BillBrook,

    BillBrook BillBrook Oct 17, 2014 10:53 AM in response to John Blanchard1
    Level 1 (0 points)
    Oct 17, 2014 10:53 AM in response to John Blanchard1

    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

  • by John Blanchard1,

    John Blanchard1 John Blanchard1 Oct 17, 2014 11:14 AM in response to BillBrook
    Level 5 (5,243 points)
    Oct 17, 2014 11:14 AM in response to BillBrook

    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.

  • by BillBrook,

    BillBrook BillBrook Oct 17, 2014 11:20 AM in response to John Blanchard1
    Level 1 (0 points)
    Oct 17, 2014 11:20 AM in response to John Blanchard1

    Really appreciate your time and insights, John.

     

    I suspect we'll all be waiting until **** freezes over before Canon fix their drivers, though... :-(

     

    Ah well.

  • by BillBrook,

    BillBrook BillBrook Oct 17, 2014 11:22 AM in response to BillBrook
    Level 1 (0 points)
    Oct 17, 2014 11:22 AM in response to BillBrook

    Are people really that offended by the H**l word that rarely freezes that Apple feel the need to asterisk it? Bizarre.

  • by John Blanchard1,

    John Blanchard1 John Blanchard1 Oct 17, 2014 11:24 AM in response to BillBrook
    Level 5 (5,243 points)
    Oct 17, 2014 11:24 AM in response to BillBrook

    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.

  • by BillBrook,

    BillBrook BillBrook Oct 17, 2014 11:30 AM in response to John Blanchard1
    Level 1 (0 points)
    Oct 17, 2014 11:30 AM in response to John Blanchard1

    The Generic PCL works, but its pretty dire quality. Printing via Windows works just fine, but I hate giving in!

  • by John Blanchard1,

    John Blanchard1 John Blanchard1 Oct 17, 2014 11:55 AM in response to BillBrook
    Level 5 (5,243 points)
    Oct 17, 2014 11:55 AM in response to BillBrook

    Bill, just to make sure, you're running the most recent drivers for this Sensys, right?

  • by BillBrook,

    BillBrook BillBrook Oct 17, 2014 12:01 PM in response to John Blanchard1
    Level 1 (0 points)
    Oct 17, 2014 12:01 PM in response to John Blanchard1

    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.

  • by BillBrook,

    BillBrook BillBrook Oct 17, 2014 12:08 PM in response to BillBrook
    Level 1 (0 points)
    Oct 17, 2014 12:08 PM in response to BillBrook

    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.

  • by John Blanchard1,Helpful

    John Blanchard1 John Blanchard1 Oct 17, 2014 1:01 PM in response to BillBrook
    Level 5 (5,243 points)
    Oct 17, 2014 1:01 PM in response to BillBrook

    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.

Page 1 of 3 last Next