Printing on Yosemite is anyone haveing problems?

I totally empathise. let's hope they sort all this soon.

Sent from my iPhone

Hi m,

I am not saying they are not aware of the problem. I was just trying to point out that answers from Apple won't be delivered here. And, for the most part, the solutions will have to come from the manufacturers, so that's a better place to start.

Hi John,

Im not questioning what you are saying in any way.

I look at it like this though. If all these printer brands are failing to print through yosemite, then in my mind the problem lies there, which I am sure the tech guys will be keen to resolve.

Regards

M

I'll throw another wrench into this already-tool-choked mess: my office has four Epson printers, all networked via either USB (shared on a local Mac) or LAN. The two WorkForce 645's survived the Yosemite upgrade just fine, but both Stylus Photo R320's stopped working. While these R320's are old, we use them constantly for printing to CD's and DVD's, and Epson does still list them with their driver updates (of which mine are already installed and up to date). Others in this forum have suggested trashing the Mac HD/Library/Printers/EPSON folder and then rebuilding it with a driver update, but that would take the two WF645's offline as well as the R320's. Since those WorkForce machines are still working, I'm very reluctant to take that risk.

Within that EPSON folder are lots of parts and pieces, so picking and choosing elements to delete and "rebuild" would be nice... but there's no apparent way to identify which elements are used for specific printer models. Ideas, anyone?

Hi hwoodlive,

I also print to DVD's using an epson xp-610. You could try using that driver when installing the R320 since they both have similar functions (printing, copying and printing CD's). There is no guarantee that it will work, but I know other people that have older printers and use a driver from a newer printer have had success.

-crazy

Cool idea, Crazygamer101... didn't work for me, but perhaps others will have better luck. The adventure continues!

Thanks for the tip.

My HP Officejet 8600 Pro worked for about one week on a new iMac 5K Retina and then on both of the new iMacs printing stopped.

Tried your idea and it works and it much faster.

UPDATE:

Using the IP method will change how you need to Scan with this particular printer. The HP Scan utility works best. Scanning directly from printer to computer works sometimes.

IMHO I think these issues are Bonjour related. Mine was working then stopped.

Sorry it didn't work for you hwood but I'm glad yours is working JP

-crazy

After 14 hours with Xerox and APPLE. printers will not work if you do not have a compatible DRIVER. XEROX does not have anything for 10.10 Yosemite...they have not built it yet...we are out of MONEY< LUCK > and Patience...at least I am....

Xerox went on to explain to me this is my fault for upgrading and if I read the fine LEGAL PRINT on my XEROX documents it would have spelled out

I am responsible.....So after spending over 450.00 in March of this year....I have no working printer...

soooooo after XEROX being a terrible disappointment.... I have gone to HP to purchase something I CAN DEPEND ON.....

I will never ever deal with XEROX again... they are more interested in their bottom line and clearly has forgotten what took them new heights can certainly bring them down...

I have cried enough tears....

Did you try deleting the Xerox printer and adding it back using it´s IP address? I had the same problem with my HP printer and it worked for me. Go to Apple preferences printers and scanners delete printer add printer choose IP on the top menu and add your printer´s IP address.

I am replying to the original post ...

I have a Kodak 9250 printer which also stopped working upon my upgrading to the Yosemite Operating System ...

Today I received a response from Kodak, which worked for my MacBookPro and Kodak 9250 printer .....

I have the suspicion that this will work for most of the folks here that have this issue ....

Here is the link to the Kodak page that has the info:

http://support.en.kodak.com/app/answers/detail/a_id/49247/selected/true

Same Problem attempting to printer. Updated to Yosemite. Also Updated Office 2010 as there was an update. After doing both. Cannot print to Sharp MX-4100 copier.

Microsoft Error
Reporting log version: 2.0

Error Signature:

Exception: EXC_CRASH
(SIGTRAP)

Date/Time: 2014-11-19
20:49:40 +0000

Application Name:
Microsoft Word

Application Bundle ID:
com.microsoft.Word

Application Signature:
MSWD

Application Version:
14.4.6.141106

Crashed Module Name:
merp

Crashed Module Version:
2.2.4.141106

Crashed Module Offset:
0x00004422

Blame Module Name:
SharpMX2700NCO

Blame Module Version:
1.3

Blame Module Offset:
0x00004394

Application LCID: 1033

Extra app info: Reg=en
Loc=0x0409

Crashed thread: 0

I have a canon MG7100 series printer. After struggling with this issue for 3 days, I changed so many settings that I wasn't sure I'd ever get my printer set up properly again. I finally used my ipad and downloaded the PIXMA/MAXIFY Printing Solutions app.

After getting it to find my printer, and get the needed information, I added the needed info about my network. It instructed me when to connect my laptop to my printer, when to restart my printer, and when to disconnect the usb connection.

I then opened the Canon IJ Network Tool and followed the instructions.

I hope this helps some that are having the same problem.

In my case, several steps solved the issue:

1. I followed something similar to this http://support.en.kodak.com/app/answers/detail/a_id/49247/selected/true, i.e. this: http://www.papercut.com/kb/Main/MacOS1010YosemiteKnownIssues

That is, I entered these commands in Terminal:

• sudo sh -c 'echo "Sandboxing Off" >> /etc/cups/cups-files.conf'
• sudo launchctl stop org.cups.cupsd

2. Then I repaired permissions on the startup disk (and it found permission problems with the "cups" folder, which is exactly where the printer drives are located that stopped working for me on Yosemite).

3. Lastly, I removed and re-added the printer. Where formally, the type of printer was not detected, it now got properly detected and printing worked, finally.

BTW,

Writing "Sandboxing Relaxed" instead of "Sandboxing Off" in the Terminal command works, too, and should be a bit "safer", I guess.