Q: Pages freezes when closing a document

We are working with a Sharp2610 and having the same issue.  Still no resolution?

The problem with using iWork '09 instead is that it would not damage your files, you'd have to put up with an extra 110 features and you would actually get your work done instead of trying to debug this and a string of other problems that are still in Pages 5 one year on.

So definitely don't go there!

Peter

Same problem, I have a Sharp too.

We are having this same problem in our school. We to have Sharp printers. My tech person changed my printer window. When you choose the drop down box next to printers, it shows the Sharp printers. She changed it to also say (nearby printers). If I choose this and then select the Sharp printer from there, everything works.

I can use Pages and print as normal. No freezes as of this point in time.

Sharp told me to try removing their printer then adding it back in and install a generic postscript printer as the driver.  This fixed the issue.  I can print to the sharp printer and then close the Pages document as normal.  At least its a work around until a new driver from Sharp comes out.

An update, running Pages 5.5.2 and 10.10.2 and the problem still exists.  I changed the driver to generic postscript and it solved this issue for me.

I'll add to the long list also.  Running a Sharp MX-3610N, been experiencing the same problem for quite some time.

Can you give the rest of us a link to what driver you used or how you went about doing this? 

Same problem for probably over a year and finally found this useful thread. 

Pages 5.5.3

Mac 10.10.4

Sharp MX 4501N

Same issue here with a Sharp MX-5141. To be able to print on this printer i have to authenticate my self with my personal identification number. With the sharp printer driver i can do so in menu item „job handling“. Is there a generic printer driver that would let me identify myself and does not cause the freezing?

We too are experiencing this problem but we use a Cannon MX890 not a Sharp copier. It started when I tried to print a document, a pretty common occurance, and I couldn't. I tried to sent the doc in an email to myself and found success but that's really too many steps for a printout. I can print if I simply hit the return button but I can't close the docs by clicking the red X. I can quit but when I relaunch, the same docs appear.

Help!!!

Thank goodness for this discovery. Still a year after your original post, this issue is still current. I was SO frustrated with Pages freezing constantly on my brand new macbook. I contacted and worked with Apple numerous times, with no results at all. They did suggest it might have been a third party problem. Finally, after searching online many times, I finally found this thread, and the fix to this terribly irritating problem. Thank you! Now to figure out how to get the printer on again, and useful so Pages doesn't freeze. Perhaps trying changing to generic postscript, suggested by Dave Razorsek here in response to JINGOES

Bad news folks. This bug now extends to Mail.app in El Capitan. If the print dialog is invoked when any message composition windows are present, those windows essentially crash, and can't be closed.

Here's how it manifests:

1. Open a new composition window, or a few.

2. Go back to the Message Viewer, select any message and hit Print. You don't have to follow through with the print. You can cancel. Merely OPENING the print dialog when certain Sharp printers are present is enough.

3. Go back to any of the previously opened composition windows and try to Send or Close them. Either action will NOT close the window, some errors will spit into Console, and you will never be able to close that window again until you quit and relaunch Mail.

Note that if you pressed Send, the message DOES get sent. This caused a lot of initial problems as if you didn't have sounds activated, or checked your Sent folder, you wouldn't know this, and commonly hit Send repeatedly!

While our Pages problem was limited to an MX-2640, this Mail problem now manifests with that printer as well as our MX-363.

Ways to avoid:

1. STOP USING SHARP PRINTERS (We haven't been able to achieve this yet, but you can be sure we'll never buy another)

2. Close any composition windows BEFORE printing

3. Quit and relaunch Mail.app after printing.

Hi Folks.

I've resolved the issue for the 10.8 - 10.10 Sharp drivers for the MX-M363N / MX-M453N printer drivers on 10.10.5 running Pages 5.6.1. It may also fix the issue for the versions you are using.

sudo mv /Library/Printers/Sharp/PDEs/SharpMXM453NWM.plugin ~/Desktop
sudo mv /Library/Printers/Sharp/PDEs/SharpMXM453NJC.plugin ~/Desktop

Copy and paste each line inidividually into a new line in your Terminal window and press enter. You'll have to authenticate as an administrator.

This does not delete the *.plugin files, but just moves them to your Desktop, in the event that removing the files cause conflicts with other applications. I'd rather not post commands that explicitly remove files if not absolutely necessary.

Additionally, if you're not comfortable with Terminal or you've installed a different version on a different OS X build, you can navigate to the folder in Finder and remove the *.plugin files that exist there.

The folder is located at /Library/Printers/Sharp/PDEs.

After I removed the two plugin files from that folder I was able to verify that the Pages crashing issue after accessing the print dialog stopped occurring.

Unfortunately, that's as good removing the print drivers for me. Those files are what creates the extra panes of the printer panel, which includes the job authentication section, which is a requirement for my organisation.

After we complained loudly (and showed them this topic), our local Sharp representative miraculously got us access to a beta driver, which resolved the issue for our MX2640, although not for our MX363.

Ah!

Thanks for the followup. Was interested in seeing what options I would be removing with that workaround. I assumed we'd lose some extra dropdown menu options in the print dialog. Guess it comes down to your environment's needs.

Shame that Sharp hasn't resolved this issue since 10.9. Issue persists through 10.11 on Mail.app, interestingly enough.

No beta drivers for the M363n? :\