FYI, I forward the mail sent by Arne de Laat on 3 Dec 2013:

Hello all,

In the e-mail from Wim when he started this group, he mentioned that there were some problems with printing in OS X 10.9:

From: Wim Heubers w.heubers@nikhef.nl

We have run in the following print problems after upgrading to OS-X 10.9:

2. The existing problem with the printer status jobs still exists, but

now you can not remove these jobs yourself anymore, which results in a unwanted delay before the print output becomes available in the printer system. We have contacted the supplier of the printer software.

-- CT Beheer Wim

I know of a way to address problem #2. These status jobs can be made visible using the CUPS web interface. To enable the interface, simply open your Terminal and enter:

cupsctl WebInterface=yes

If you ever want to disable it, simply use the same command but with 'no'

The CUPS web interface can be reached in your browser via: http://localhost:631

The interesting page here is: http://localhost:631/jobs/

When you start a print job those 'status jobs' will be visible on that page

Cancel all the jobs with a size of 1k, the interface will ask for you username and password once. Once all those status jobs have been canceled your real job will start printing.

Thanks to dr. David Fokkema for figuring this out.

Greetings, Arne

On 13 Jan 2014, at 10:38 , Jacco de Vries jdevries@nikhef.nl wrote:

Hi,

I had the same problem. Reinstalling the drivers worked for me, for follow-you printing.

The generic Postscript solution from Jeroen also worked great for me, for direct printing.

Cheers, Jacco

On 13 Jan 2014, at 9:57 , Jeroen Van Tilburg jeroen.van.tilburg@cern.ch wrote:

...

Hi,

I have installed the Nikhef printer (N2 for what it is worth) as a generic Postscript printer. That works without problems. I know that Gerhard had problems when installing the “proper” drivers.

Cheers Jeroen

On 13 Jan, 2014, at 09:40 am, Harry van der Graaf vdgraaf@nikhef.nl wrote:

...

I installed Maverick on my (office) miniMac and my MacBook Pro. It looks like printing does not show the two ‘halt’ jobs anymore, but the delay is still there, and can not be dropped……

Re-installing a printer does not help.

?

Harry _______________________________________________ Macos-users mailing list Macos-users@nikhef.nl https://mailman.nikhef.nl/mailman/listinfo/macos-users

---

Macos-users mailing list Macos-users@nikhef.nl https://mailman.nikhef.nl/mailman/listinfo/macos-users

I had the same thing. AFAICT a corrupt installation somehow. I had to remove all traces of Adobe Reader (which was not for the faint of heart) and then re-install. you'd need to use spotlight to find Reader related stuff and delete it, get the rest of the crud via

find /Library -name *com.adobe*

deleting the things that have to do with adobe reader (there might be other non-reader adobe crap, be careful), you'll need to do that with

sudo rm <name of file here>

then repeat this process

find ~/Library -name *com.adobe*

you can rm those files without sudo. Be careful with embedded spaces in the commands :-)

JT

On Feb 3, 2014, at 09:38 , Harry van der Graaf vdgraaf@nikhef.nl wrote:

If I want to check in for an easy jet flight, I get a window from Adobe Reader telling that I should install version 11. After doing that, the same window pops up. I can’t get around it. This occurs on my MacBook Pro and on my mini-Mac (both Maverick).

?

Harry _______________________________________________ Macos-users mailing list Macos-users@nikhef.nl https://mailman.nikhef.nl/mailman/listinfo/macos-users

With Maverick, I have problems with reading, copying and saving pdf files since I installed a new version of AdobeAcrobat some three months ago. Am I the only one?

Regards,

Harry

On 14 Jul 2014, at 11:20, Arne de Laat adelaat@nikhef.nl wrote:

What exactly is the problem? Is it slow? Does it produce errors? Are files being corrupted? Does it simply not work? Which version of Acrobat do you use?

Can you you alternative programs or do you have to use Acrobat? Apple Preview is not a bad pdf viewer/editor/annotator/exporter..

The problem is solved. Acrobat uses a tab in Safari to display the downloaded PDF and Safari doesn’t know there’s something in the tab. Consequently, when you do a Save As from Safari’s menu the PDF is zero bytes long (Safari hasn’t got the file, Acronbat has it!).

The solution: use the Safe File from the Acrobat plug-in. The resulting PDF will have the proper length and will display fine.

—kees