Yosemite breaks Ricoh/Lanier Aficio SP C240DN

Hi all,


Upgraded my late 2012 Mini to Yosemite, getting "Stopped - 'Filter' failed" when trying to print to my C240DN. The same occurred with the Yosemite betas and resolved with Mavericks. I've installed the both the Ricoh and Lanier driver updates to no avail as the C240DN is not supported by them. I'm using the latest available Mavericks driver from the Ricoh/Lanier site.


Any help greatly appreciated, thanks!

Mac mini (Late 2012), OS X Yosemite (10.10)

Posted on Oct 16, 2014 7:40 PM

Reply
80 replies

Oct 29, 2014 12:09 PM in response to drmcf

Hey there- Ricoh tech (and Apple user) checking in.


This is the first I've heard of this, because in our area we got our first service call for this today. This isn't unusual. Apple makes changes and expects the world to change around them. The last time it was SMB scanning- one day it worked, the next day it didn't. Poof! From a troubleshooting point of view, if your printer worked yesterday, and everyone else's printer worked yesterday, but today everybody upgraded to Apple's new OS and now printing doesn't work? That's not a problem with your printer. That's a problem with your software. And I'll be very surprised if Apple provides a patch to support any sort of legacy procedure they've decided to change or eliminate because that's simply not how they roll. In my experience, Ricoh will eventually update printer firmware or update the printer drivers to accommodate Apple's changes. But it might never get fixed for older devices. Sometimes Apple makes changes so drastic that older hardware can't be modified to support their whims (see: SMB scanning.)


So on behalf of Ricoh, sorry for the inconvenience. It's possible Apple explained these changes months ago to our engineers and they have sat around doing nothing. But it's also possible Apple simply rolled out their changes without a care in the world for whether or not it breaks their customers' workflows. I really have no way of knowing, and neither will any of the other boots in the field guys who will ultimately wind up being dispatched to address this situation.


I can tell you Windows users are still working fine. So if you can dual boot, you can try to print from that environment. It might work. And there might be some ninja terminal workaround that will get you working again. But I don't know that, either. I only mention it because if you do find a workaround, please share it and document it. And keep that documentation, because it's entirely possible that when Ricoh does provide an official, supported update, you might have to undo the workaround to get it to work.

Oct 29, 2014 2:34 PM in response to drmcf

Let's be clear. I am a Ricoh TECH. I'm one of the guys that responds to YOU, the end user, when things don't work. If I represent anyone it's you, and other techs like me. When end users take it in the chin because Apple broke their flow, we take it in the chin, too. And we take it in the chin from the end users, too. And that's sort of the raw deal part for me- I literally spend every day of my life working to solve your problems.


But Apple broke your printing. PERIOD. I wish I had a magic wand to wave to magically make that unhappen, but I don't. If you check Google, you'll see problems reported for HP, Lexmark and a lot of others too. It's not just Ricoh. Apple fundamentally changed how their devices connect and communicate with print devices. AGAIN. And when it gets fixed, historically it has always been Ricoh that fixes it, not Apple.


If you're going to let the facts here affect your future actions, logically you should shy away doing OS updates until you're aware of the problems that can result. I first became aware of this Apple update phenomenon in the 90's when my shiny new Voodoo graphics card got glitchy because Apple decided not to support it any more. Some things never change. That's why I'm still running 10.9.


I can and will update here with any info I get if and when it becomes available. And for what it's worth, today is my day off. I'm trying to figure out anything I can about this just like you guys are. I'm trying to get ahead of this because I am sure the coming weeks and months will be full of Apple printing issues for me. The official word at this time from our support and engineering teams is that 10.10 is not an officially supported OS. And I am sorry about that- as a "representative of Ricoh," as a fellow Apple guy, and also just as a dude at his computer.

Oct 29, 2014 3:30 PM in response to Sargasmic

I do have respect that you take your time to inform us about this issue, but i have my doubts about the profesionality about the way you are doing this from the view of your company (in this i mean Ricoh)

Giving the blame to apple is not verry realistic, as the rollout of Yosemite has been issues already for months and also Ricoh was informed and has been part of the Beta test group. The issue was know also in this period. So no; don't blame apple.


Advising to use Windows to an Apple user is the same as the mechanic is telling you that have to move to a different house when the heating broke down; if this is your advise i think you have to find a new job!

Telling us when the update of the driver will be available, and find a temporary (good) solution for the meantime is what your customers are looking for.

Oct 29, 2014 5:46 PM in response to TheRoySit

Look- I'm just a guy on his computer on his day off. I apologize if I am not "professional" enough for you.


Ricoh's official statement is that 10.10 is not a supported OS. So MY official stance is that 10.10 is not a supported OS. And anything else I say is my own opinion that is in no way supported or condoned by Ricoh or any of its affiliates both foreign and domestic.


Is that better? I don't think so. It puts the blame on YOU for updating. So let's dig deeper instead. But now you just get me. I'm not speaking as a Ricoh rep, I'm speaking as a grumpy old tech who knows too much about Ricoh machines and has dealt with Apple for many years.


First of all I think you're making a LOT of assumptions, but let me play devil's advocate for a minute: you say Ricoh has been working with the Yosemite beta for months. I'm not in a position to comment on that, but I am in a position to relay that Ricoh's official stance is that 10.10 is not a supported OS. And if Ricoh was working with Apple, we can assume Apple knew Ricoh did not support Yosemite, but they released it anyway- and you say it was a KNOWN issue. That means Apple KNEW it would break printing on Ricoh devices. And they released it anyway. There's also issues with HP, Lexmark, Xerox, Dropbox and many others. Were they not part of the beta program?


Did printing work before the 10.10 update? Yes. Does it work after the update? No.


Did the printer change? No. Did the software change? YES.


Troubleshooting 101: The software changed, so the problem lies with the software.


Can Ricoh fix the software? No. Will Apple fix it? Look- I don't want to seem cynical, but if this change is like every other change Apple has made that affects hardware operation and device connectivity, this WAS the fix. They decided there was a "better" way to do things, so now that's the way it's going to be done, and the world must change to accommodate them.


So Ricoh must find a way to make their machines work with the new software. But what will that take?


If you open a web browser and put the Printer's IP address (or hostname) in the address bar, you SHOULD see the printer's web image monitor. Before the update, that worked. After the update, it does not on any of the models we've tested. So what does that tell us? It tells us a few things- the main takeaway is that the computer is no longer able to establish a connection with the printer. And I don't know why that is.


But it suggests quite strongly that a simple print driver update is unlikely to fix anything. Browsing to the HTML files embedded in the device's controller has nothing to do with the print driver. And that means the fundamental connection between the two devices simply isn't happening- so it's likely the firmware must be updated to address whatever change Apple made. But first it must be written- and it is written for specific hardware. And each model of machine has different firmware, and Ricoh has dozens of models, hundreds if you look past current-gen models in production now (spoilers: most people are using older devices no longer in production.) And let's further consider that Apple has in the past made changes that were impossible to address with certain hardware configurations- especially older equipment. This isn't the first time that something that worked fine for years suddenly stopped working overnight because Apple changed something. And for older machines, it might mean it will never work again. And remember- NOTHING changed on the Ricoh device. It's the same as it ever was, only now it might not work ever again.


And don't forget, firmware updates aren't really meant to be performed by the end user. So there's that.


But let's also consider if a print driver update is necessary (to fix the issue or maybe as an addition to a firmware update.) Apple prints to Ricoh devices using Postscript. If THAT needs to be updated, we're looking at 3rd party licensing fees as well as looking to Adobe to now update Postscript. This is probably unnecessary. Probably. But there's still the task of updating the code on what could turn out to be literally hundreds of print drivers- and the newest most profitable models are sure to be addressed first .


So to simplify greatly- for Ricoh to "fix" the "problem," here is what is likely to be required:


1) Code updates for firmware for dozens of different device types currently in production (and likely multiple updates per machine)

2) Possible updated 3rd party licensing per device (Adobe) as well as possible 3rd party software updates

3) Updated print drivers for every supported device

4) Repeat all of this for legacy models, if it's even possible.


And this doesn't even begin to touch on the possible complications from the connectivity changes for Java and other 3rd party applications.


And why? Because Apple changed... something. For... reasons. I'm sure they're good ones, too.


So let's keep playing devil's advocate. Let's say Ricoh DID have their hands on the Yosemite beta months ago. And to keep playing, we have to assume nothing changed in the Yosemite build that pertains to device communication or printing. So Ricoh is the bad guy because... they didn't seamlessly produce all of these updates in... months?


Look- I know I seem a bit hostile. But at this stage I still don't know what Apple changed, or what their compelling reason was for changing it. But whatever it was, it's going to require a TON of effort from every level of the Ricoh organization to "fix" and that's for (and I'm being generous here) maybe 5% of Ricoh's customers. All of this has happened before, and it will happen again.


I wonder why nobody ever asks why Apple doesn't provide legacy support instead of just breaking things they don't like any more. And some days I'd almost bet that at least for some Apple users, if their laptop battery exploded and killed half their family they'd sooner sue the power company for bad electricity than consider Apple might be at fault.

Oct 29, 2014 6:52 PM in response to Sargasmic

Sargasmic, I appreciate your giving us the Ricoh side of things and your thoughts. If it helps with the troubleshooting process, I actually have been able to get to the web image of my printer by putting the IP address in the web browser. (I'm printing to a Ricoh Aficio MP C3001.) I've been able to print using the Generic PCL driver, but in black and white only. Using the Generic Postscript driver just spits out loads of white paper from the printer. Using the Ricoh drivers, I either get a "printer is not responding" message, or the job "prints" but nothing actually comes out of the printer.

Oct 30, 2014 5:39 AM in response to C2_41

If you can connect and print using PCL, that's great news. It's not supported by Ricoh at all, but it is one option to try.


For anyone unaware of what this entails, when adding a new printer from system preferences, there is a menu at the bottom of the window (you might need to expand to see it) that says "USE:" and it's where you choose the print driver. You can try "Generic PCL driver." Most Windows users use PCL to print and they are unaffected. I would also recommend using the printer's IP address and putting it in manually rather than allowing Bonjour to connect automatically (maybe it will work, maybe not. If we're looking at communication problems, I'd avoid anything that is supposed to work "automagically.")


This won't allow you to print in color, though- for that you would need a PCLC driver (like PCL5C) and none of that is built in to the Mac OS, and none are provided by Ricoh. Don't ask me why- Ricoh has never had anything other than Postscript drivers for Mac and I'm sure it has a lot to do with rights, permissions and licensing.


I haven't tried it myself, but it is worth experimenting with other manufacturer's color PCL drivers to see if you have any success. In the past HP drivers have worked, but it is my understanding that HP is having the same issues as Ricoh with the Yosemite update, but it's possible it is only Postscript and PCL is unaffected? At this stage I have no idea.


Just keep in mind using generic or off-brand drivers might allow you to print, but the supported drivers from Ricoh are what will have the code to allow stapling, hole punch, sorting, and any other functions your device might have.


Another thing I can suggest but not help with is Ghostscript. I have seen many articles over the years about using Ghostscript to configure color PCL drivers using CUPS for Linux and OSX. But I've never tried it.


If you are sending jobs using a generic Postscript driver and getting blank pages (are they blank or is there gibberish at the top?) it usually means the printer is not Postscript compatible. If you always used Postscript to print before and now it's not working it could mean this change Apple introduced is specifically breaking Postscript. And if that's the case we might be looking to Adobe for their fix before Ricoh can get to theirs, but I digress.


And if your job "prints but nothing comes out of the printer" your problem might be USER CODES or some other permission issue. IIRC correctly on the Ricoh Postscript driver you would input your user code under "Job log" in the print interface. But that option might not be there in off-brand or generic drivers. I'm surprised you're even communicating with the printer at all, C2_41. But I haven't seen any other discussion about the C3001 or that generation of devices at all.


As far as intruder1400's question about shared drivers from a NAS or server, you can't print from a NAS. But there's (probably) no reason you can't print through a print server. But those can be configured a number of different ways, so I can't offer specific directions other than try it because it should work. That's if you're already running a print server. Most of the time you can go to the add printer interface from system preferences and select the "Windows" button at the top to display any shared printers that are configured. If you're using any other kind of server I can't help you.


Some other things to try if your device supports it:


Airprint. If you have to ask, you probably don't have it. It's baked in to OSX but it's still an add-on for Ricoh devices that has to be configured, and it's only supported on the newer models.


Hotspot printing. Again- if you have to ask you probably don't have it. But this bypasses the "normal" way jobs get sent so it is worth setting up if you can (check your manual.)


If you have a newer multifunction device, you can put your file on a usb flash drive or SD card and print from that via the "Printer" interface at the Ricoh device. Standalone printers (like the c240dn that this is thread is about) don't usually have this, though.


So good luck, folks. I'll update if I learn more.

Oct 30, 2014 10:09 AM in response to Sargasmic

Apple changed the security model for printer drivers in 10.10. This was a deliberate change to eliminated the possibility of 3rd parties from collecting and harvesting personal data from the print stream. This was part of a two year effort. Apple engineers were in Japan (and all over the world) in 2013 and 2014 explaining this to every major printer vendor, including Ricoh. Most have responded by release secure drivers, some in 2013! Some chose, for their own business reasons, to delay making the required security improvements. Apple is not planning to relax the security model, so you are reliant upon the schedule of your printer manufacturer to release updated printer drivers. If your vendor has not yet done so and your printer is no longer working, I feel your pain. Please work with your vendor on their release schedule, or try AirPrint, or one of the posted work-arounds.

Nov 7, 2014 3:05 AM in response to intruder1400

Hi together, sorry about my lousy English, too!


Did anybody find a functional solution yet?

I've got an aficio sp c240sf, i bought it at beginning of this year and i can't accept not being able to print with yosemite.


Now the decision:

  • keep on waiting for new driver support (how long???) or
  • buy a new driver and kick the ricoh through the window ...


My hope getting an functional driver in a short time is shrinking dramatically. Is there any other opinion about this? Not being able to print isn't an option.


Choosing the other option: what mf-color-laser-printer do you recommend for working with yosemite in a small office regarding costs for purchase and toner?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Yosemite breaks Ricoh/Lanier Aficio SP C240DN

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.