-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
homebrew installed ghostscript 8.70 broke all printing on MBP (snow leopard) #528
Comments
Seems extremely unlikely. Still you could help us out with some more information. Like what version of OS X you are on and where you installed Homebrew. |
10.6.2, homebrew is in /usr/local, and I correctly set all permissions to make the directory user writable. FWIW, I reinstalled imagemagick (and thus ghostscript) using http://github.com/masterkain/ImageMagick-sl and everything worked fine, even though the script uses ghostscript 8.7 as well. I noted that the homebrew formula uses a different (and much more complicated) set of options to ./configure... |
Here is what the errors in the printer's error_log looked like prior to uninstall (yes, it took me a month to figure out what was going on):
|
Here is the (long) output from /usr/bin/env (though this is post-fix):
|
wtf: |
Well I just searched my system. Ghostscript does not come with OS X. So it is really a mystery why the OS X cups print system uses it and then breaks. |
yea, its weird, and annoying. I searched all of /library and ~/library looking for a reference to /usr/local/bin/gs without success. Its a mystery to me why it is doing that. I did google for the error and found some refs to a similar problem on linux boxes when ghostscript was installed. |
Seems like a bug in cups then. I hate ghostscript. Does anyone even use it with imagemagick? I'm tempted to remove it as a dep from imagemagick. |
I don't use it, that's for sure, so I wouldn't miss it if it was gone. |
Turns out I was thinking ahead, it already defaults to not depending on gs for some time now. So I'll close this as most likely a bug in OS X itself. |
Printing worked fine for me after installing gs. And ImageMagick (also installed with brew) trying to call gs is what prompted me to install it...FWIW. |
This may be no longer needed, but the Ghostscript install asked for feedback, so here's mine. I'm on a MBP that I just updated to Snow Leopard. I just installed gs and printing is fine. |
Also just installed ghostscript with brew, printing still working here. |
Printing fine here too |
Printing still works fine (10.5.8, even after a reboot), OTOH, the tool that prompted me to install GS in the first place still doesn't work because now it says it can't find Arial:
..but that might be completely unrelated (EDIT: yes unrelated, has to do with http://gothick.org.uk/2008/03/14/using-os-x-fonts-in-imagemagick/ which magically solved itself after |
Printing works fine for me after install of ghostscript (at least to my proprietary drivers for my canon multi-function laser). OS X 10.6.3. |
Printing works fine for me as well. However, seeing the message that you might have broken my printing capabilities after the installation was complete was a little panic inducing. |
Hey, it didn't break my printing! I haven't rebooted yet though. I've got an HP printer, FWIW and OS X 10.6.4. @mxcl - I use ghostscript w/ imagemagick and paperclip for thumbnailing and general conversion of PDF files. |
my printing seems fine after installing. os x 10.6.4, brother mfc-240 via networked windows machine |
Prints ok on 10.6.4 OSX with ghostscript 9.0. (via network windows machine) |
No problems printing on 10.6.4 with ghostscript 9.0 |
Okay so MAYBE it's time to close this ticket? Or at least update the text and declare the 10.6.4 / 9.0 combination to be known stable? :-) |
+1 on closing |
Printing is fine for me too. (Just a quick test, post-install, using a Postscript printer.) Running Mac OS 10.6.5. |
I don't like closing tickets that we never really understood. But yeah. It's old and no new reports for ages. |
OS X 10.6.4 / GS 9.0 and everything seems to be working OK. +1 on closing. |
Downloading => http://ghostscript.com/releases/ghostscript-9.00.tar.bz2 +1 closing |
FYI this ticket is already closed. |
I know this ticket's already closed, but it's worth noting that the full TeX Live bundle for Mac OS X, which hundreds of people have installed, puts its own copy of GhostScript (8.64, iirc) at /usr/local/bin -- so it must not cause a printing issue for very many people! |
Documents would just sit in the queue, forever.
Fixed it by removing ghostscript and rebooting.
The text was updated successfully, but these errors were encountered: