Apple Intelligence now features Image Playground, Genmoji, Writing Tools enhancements, seamless support for ChatGPT, and visual intelligence.

Apple Intelligence has also begun language expansion with localized English support for Australia, Canada, Ireland, New Zealand, South Africa, and the U.K. Learn more >

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.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Ricoh MP C2500 not printing after upgrading to Yosemite

I have a Ricoh MP C2500 (installed on my network in the office) that was working perfectly in Mavericks before I upgraded to Yosemite.


I was using the drivers via the Linux Foundation (Foomatic, Ghostprint, PXLmono) and everything was working perfect.


It seems that there has to be an update for these drivers for Yosemite.


The official driver from Ricoh doesn't work, nor has it ever worked because I don't have the PS module for the Ricoh.


Any help would be greatly appreciated!


MacBook Pro, OS X Yosemite (10.10)

MacBook Pro with Retina display, OS X Yosemite (10.10)

Posted on Oct 20, 2014 6:57 AM

Reply
134 replies

Jan 7, 2017 3:50 AM in response to thomas178

The approach suggested by thomas178 worked in Sierra for a Samsung ML-1210. Copying the files from /usr/local/bin to /usr/libexec/cups/filter is the key as far as I can tell.


I believe a fresh install would also work; You know it's done right when the name of the driver changes to include `(Yosemite Modified)`


I must add I'm happy as a clam now with the ability to print from my mid 2015 macbook pro onto this printer that will go down in history as the best personal laser ever made.

Nov 14, 2017 8:16 AM in response to Saior23M

Hi Vic,


sorry I rarely visit this topic anymore.


Following thomas178's description step-by-step should make the printer work for you.

Fresh start:

1) installed foomatic, GhostScript 9.19, and pxlmono in that order

2) went to /usr/local/bin and copied foomatic and all the 'gs' files to /usr/libexec/cups/filter

3) in Printers & Scanners, added my printer: IP / LPD / PXL driver

4) ran your script (this still didn't get me printing, so then I tried Sauva's ninja trick from page 8 of this thread):

5) In Terminal, typed

sudo pico /etc/cups/cups-files.conf

arrow down all the way to the bottom of the file and on a new line add this string

Sandboxing Relaxed

^X and save the edit. Then fire off this command:

sudo launchctl stop org.cups.cupsd


Hope it will work for you too, cheers!

Oct 21, 2014 9:52 AM in response to antonislatouros

I believe I have a temporary fix (patch) for many of those that use foomatic-rip. It should work with Ricoh printers. You can get it at http://tinyurl.com/oepe5go Once you have downloaded it, double click on it to unzip it. The file you want to work with is yosemite_foomatic_paths.command. You should right-click on the file (control-click) and choose open. Gatekeeper will otherwise prevent it from running. A Terminal window will open. Just follow the instructions. You should be able to print when done.


Please let us know if it works for you.


This script should work on those that use the pxlmono/pxlcolor, hpijs, and samsung-gdi driver packages. It will not work for the m2300w driver at this point. I hope to be able to figure that one out too, but don't count on it.


NOTES:

1. Even after this patch is applied, there will still be sandboxing notifications on the Console. Both foomatic-rip and ghostscript will eventually have to be modified to accommodate the new sandboxing rules.


2. In Yosemite, foomatic-rip has been prevented (sandboxed) from reading its configuration file. It couldn't then find any other files such as ghostscript that it needs to function. The patch modifies the PPDs for the current printers so that they provide the path to ghostscript. Similarly, ghostscript has seemingly been prevented (sandboxed) from inheriting the PATH of foomatic-rip. The patch will also add the full path to hpijs in the appropriate PPDs. I don't believe this patch really violates the intent of the current sandboxing as the PPDs are specifying the exact files to use.

Oct 24, 2014 9:36 AM in response to antonislatouros

Hey there


Here is my solution to the Yosemite vs. hpijs case (also called "filter failed").


The problem seems to be the stronger sandbox in Yosemite.
Software in /usr/local/bin is no more executed.

But that is where the hpijs package roams.


So, what is there ? (among a lot of other stuff)

And where to put it ?

Actually the whole things is started from /usr/libexec/cups/filter.

There is a link in this folder to foomatic-rip in /usr/local/bin.

So, the idea was to copy the original into the location of the link.

(I renamed the foomatic-rip-link in the target dir before, but…).

Which you can do, but it won't help. ( still "filter failed"-message )

What else is in /usr/local/bin ?

Hey look !

There are some gs*-files.

There is hpijs, too.

Which might be - together with foomatic-rip - the full load of the hpijs printing solution.


So I copied these

( meaning : all five or so files starting with gs, foomatic-rip and hpijs )

over to usr/libexec/cups/filter


AND THAT DID IT.


When testing, a first time the printer driver will say it has to correct access on the driver

which it does and then is ready to print on the next go.


on my tab:

I have a HP Deskjet 1220C (the one that does A3)

and think it is a BITTER PILL,

that HP can not support this machine on actual OS X ( for years now ),

just because they go cups.

The printer was expensive and a PRO style gadget

and - most important - still works perfectly.

They built it to last and then the wind blew them elsewhere.

Go your way HP. And thanks to the people who did hpijs.


mitch

Ricoh MP C2500 not printing after upgrading to Yosemite

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