Known Issues when upgrading macOS

KB Home   |   Known Issues when upgrading macOS

Main.KnownIssuesOnMacOsX History

Hide minor edits - Show changes to markup

November 13, 2019, at 12:27 AM by Dug - Added the word Mac and emboldened “not on every workstation” to the section on paused queues
Changed line 51 from:

Note: This applies to a Primary or Secondary Mac server installation where the PaperCut Print Provider is running to monitor print queues - not on every workstation, unless the PaperCut Print Provider is installed there too

to:

Note: This applies to a Primary or Secondary Mac server installation where the PaperCut Print Provider is running to monitor print queues - not on every workstation, unless the PaperCut Print Provider is installed there too

November 13, 2019, at 12:03 AM by 193.114.149.158 -
Changed line 51 from:

Note: This applies to a Primary or Secondary server installation where the PaperCut Print Provider is running to monitor print queues - not on every workstation, unless the PaperCut Print Provider is installed there too

to:

Note: This applies to a Primary or Secondary Mac server installation where the PaperCut Print Provider is running to monitor print queues - not on every workstation, unless the PaperCut Print Provider is installed there too

October 03, 2019, at 11:46 PM by timg - Updated with note about client-local-install script.
Changed lines 55-57 from:

Solution:

  • Re-run the Control Printer Monitoring.command - which will ask you if you want to update your CUPS sandboxing settings. Type ‘y’ and Enter. Once this is done, printing should work again.
to:

To resolve this, re-run the Control Printer Monitoring.command - which will ask you if you want to update your CUPS sandboxing settings. Type ‘y’ and Enter. Once this is done, printing should work again.

client-local-install script does not run successfully


The client-local-install script to install the macOS client will no longer work on macOS Catalina, since it is still 32-bit.

The workaround, and much simpler way to install the macOS client is to copy the PCClient.app from the server, to the local /Applications folder - as you would do with other macOS apps. The PCClient.app will then run successfully (you will have to right-click the app and select open, then open again the first time you run it - as detailed above).

October 03, 2019, at 08:43 AM by timg - Added notes about Catalina.
Changed lines 16-24 from:
to:

Most of the current changes focus around ‘notarization’ (basically, signing the apps and installers used for different apps).

The following have been notarized successfully and have been released in the latest live update. That will mean that when installing / using these on Catalina, you will not have to use the right-click → open → open workaround mentioned further down.

  • Mobility Server for macOS (see release notes)
  • Mobility Known Host client for macOS (see release notes)
  • Print Deploy Cloner tool (see release notes)
  • Print Deploy Client (see release notes)
Changed line 44 from:

Installing the Application Server, Site Server, Secondary Server, Mobility Print server, Print Deploy Cloner Tool or Print Deploy Client tools produces a Gatekeeper error.

to:

Installing the Application Server, Site Server or Secondary Server produces a Gatekeeper error.

Deleted lines 50-51:

Full Support For macOS 10.11 and above was added in PaperCut version 15.2. Make sure that you’re running PaperCut version 15.2 or later where possible.

September 24, 2019, at 05:21 AM by timg - Updated for Catalina
Changed lines 5-7 from:



to:

Added line 11:
Changed line 13 from:
to:

\\

Added line 16:
Changed line 18 from:
to:

\\

Changed lines 31-34 from:

We are actively working to notarize our apps with Apple, so that this workaround will not be required. We’re hoping to have this completed for an upcoming release of PaperCut.

This will also happen if you are trying to install the PaperCut Application Server, Site Server or Secondary Server packages, and the same right-click / control-click → open → open workaround will work here too

to:

Note: We are actively working to notarize our apps with Apple, so that this workaround will not be required.

We’re hoping to have this completed for an upcoming release of PaperCut.

Installing the Application Server, Site Server, Secondary Server, Mobility Print server, Print Deploy Cloner Tool or Print Deploy Client tools produces a Gatekeeper error.


Similar to the error mentioned above with Gatekeeper, the same will also happen if you are trying to install any of the other PaperCut packages (App Server, Secondary Server / Print Provider) and others - in this case, the same right-click / control-click → open → open workaround will work here too.

Changed line 42 from:
to:

\\

Added lines 53-59:

macOS 10.14 (Mojave)

When upgrading to 10.14 - Printers get paused, and jobs are not logged in PaperCut

Deleted lines 60-65:


macOS 10.14 (Mojave)

When upgrading to 10.14 - Printers get paused, and jobs are not logged in PaperCut

Added lines 71-77:

macOS 10.13 (High Sierra)

When upgrading to 10.13 - Printers get paused, and jobs are not logged in PaperCut

Deleted lines 78-83:


macOS 10.13 (High Sierra)

When upgrading to 10.13 - Printers get paused, and jobs are not logged in PaperCut

Added lines 90-95:

macOS 10.12 (Sierra)

When upgrading to 10.12 - Printers get paused, and jobs are not logged in PaperCut

Deleted lines 96-101:


macOS 10.12 (Sierra)

When upgrading to 10.12 - Printers get paused, and jobs are not logged in PaperCut

Added lines 109-115:

macOS 10.11 (El Capitan)

When upgrading to 10.11 - Printers get paused, and jobs are not logged in PaperCut

Deleted lines 116-121:


macOS 10.11 (El Capitan)

When upgrading to 10.11 - Printers get paused, and jobs are not logged in PaperCut

Changed lines 127-129 from:



to:

Changed line 136 from:
to:

\\

Changed line 161 from:
to:

\\

Changed line 169 from:
to:

\\

Added lines 180-185:

macOS 10.9 (Mavericks)

Apple Mac OS 10.9 update causes PaperCut’s Application Server to be unresponsive (Resolved in PaperCut 13.5 Build 24862)

Deleted lines 186-191:


macOS 10.9 (Mavericks)

Apple Mac OS 10.9 update causes PaperCut’s Application Server to be unresponsive (Resolved in PaperCut 13.5 Build 24862)

Added line 195:

\\

Added line 199:

\\

Added lines 208-214:

macOS 10.6.8 (Snow Leopard)

CUPS backends failing in 10.6.8

Deleted lines 215-219:


macOS 10.6.8 (Snow Leopard)

CUPS backends failing in 10.6.8

Added line 226:

\\

September 17, 2019, at 12:08 AM by timg - Updated with gatekeeper impact on PCClient
Changed lines 1-2 from:

(:title Known Printing Issues when upgrading macOS :)

to:

(:title Known Issues when upgrading macOS :)

Added lines 13-30:

Gatekeeper blocks the PaperCut Client from running (and also blocks the installers from running).

With the new notarization requirements that Apple are putting in place for macOS 10.15, when you run the PCClient.app on a workstation, you will receive a warning:

PCClient can’t be opened because its integrity cannot be verified

As a temporary workaround, instead of opening the PCClient.app normally, you will need to right-click or control-click the PCClient.app, and then select Open from the menu, and then again select Open from the subsequent popup:

The client will then run as normal, and from this point you can open the client using the normal method.

We are actively working to notarize our apps with Apple, so that this workaround will not be required. We’re hoping to have this completed for an upcoming release of PaperCut.

This will also happen if you are trying to install the PaperCut Application Server, Site Server or Secondary Server packages, and the same right-click / control-click → open → open workaround will work here too

September 09, 2019, at 04:03 AM by timg - Merging macOS Known Issue pages
Changed lines 1-6 from:

(:title Known Printing Issues on Mac OS X :)

Below are a list of known issues which have been noticed on various releases of Mac OS X which affect printing but are not directly caused by PaperCut.

CUPS backends failing in 10.6.8

to:

(:title Known Printing Issues when upgrading macOS :)

Below are a list of known issues which have been noticed on various releases of macOS which can impact printing, due to operating system updates / CUPS configuration changes during the upgrade.



macOS 10.15 (Catalina)

Note around Catalina (10.15) Support.

We have been actively testing the Catalina beta builds with PaperCut, and we are making changes to fully support Catalina in an up-coming release.

When upgrading to 10.15 - Printers get paused, and jobs are not logged in PaperCut

Full Support For macOS 10.11 and above was added in PaperCut version 15.2. Make sure that you’re running PaperCut version 15.2 or later where possible.

Note: This applies to a Primary or Secondary server installation where the PaperCut Print Provider is running to monitor print queues - not on every workstation, unless the PaperCut Print Provider is installed there too

The latest version of macOS (10.15 - otherwise known as ‘Catalina’) now includes CUPS version 2.3.0. When upgrading from previous versions of OSX, some of the CUPS config files will get re-written. Symptoms of the issue include filter errors appearing in the Print queue window on the Mac, and the print queues will go into a paused state.

Solution:

  • Re-run the Control Printer Monitoring.command - which will ask you if you want to update your CUPS sandboxing settings. Type ‘y’ and Enter. Once this is done, printing should work again.



macOS 10.14 (Mojave)

When upgrading to 10.14 - Printers get paused, and jobs are not logged in PaperCut

Full Support For macOS 10.11 and above was added in PaperCut version 15.2. Make sure that you’re running PaperCut version 15.2 or later where possible.

Note: This applies to a Primary or Secondary server installation where the PaperCut Print Provider is running to monitor print queues - not on every workstation, unless the PaperCut Print Provider is installed there too

The latest version of macOS (10.14 - otherwise known as ‘Mojave’) now includes CUPS version 2.2.9. When upgrading from previous versions of OSX, some of the CUPS config files will get re-written. Symptoms of the issue include filter errors appearing in the Print queue window on the Mac, and the print queues will go into a paused state.

Solution:

  • Re-run the Control Printer Monitoring.command - which will ask you if you want to update your CUPS sandboxing settings. Type ‘y’ and Enter. Once this is done, printing should work again.



macOS 10.13 (High Sierra)

When upgrading to 10.13 - Printers get paused, and jobs are not logged in PaperCut

Full Support For macOS 10.11 and above was added in PaperCut version 15.2. Make sure that you’re running PaperCut version 15.2 or later where possible.

Note: This applies to a Primary or Secondary server installation where the PaperCut Print Provider is running to monitor print queues - not on every workstation, unless the PaperCut Print Provider is installed there too

The latest version of macOS (10.13 - otherwise known as ‘High Sierra’) now includes CUPS version 2.2.x. When upgrading from previous versions of OSX, some of the CUPS config files will get re-written. Symptoms of the issue include filter errors appearing in the Print queue window on the Mac, and the print queues will go into a paused state.

Solution:

  • Re-run the Control Printer Monitoring.command - which will ask you if you want to update your CUPS sandboxing settings. Type ‘y’ and Enter. Once this is done, printing should work again.



macOS 10.12 (Sierra)

When upgrading to 10.12 - Printers get paused, and jobs are not logged in PaperCut

Full Support For macOS 10.11 (El Capitan) and above was added in PaperCut version 15.2. If possible, please upgrade to version 15.2+.

Note: This applies to a Primary or Secondary server installation where the PaperCut Print Provider is running to monitor print queues - not on every workstation, unless the PaperCut Print Provider is installed there too

The latest version of macOS (10.12 - otherwise known as ‘Sierra’) now includes CUPS version 2.2. When upgrading from previous versions of OSX, some of the CUPS config files will get re-written. Symptoms of the issue include filter errors appearing in the Print queue window on the Mac, and the print queues will go into a paused state.

Solution:

If you’re running PaperCut version 14.3 or above, simply re-run the Control Printer Monitoring.command - which will ask you if you want to update your CUPS sandboxing settings. Type ‘y’ and Enter. Once this is done, printing should work again.

If you’re running PaperCut version 14.2 or below, you’ll need to upgrade to the latest version as detailed on the Upgrading PaperCut page.



macOS 10.11 (El Capitan)

When upgrading to 10.11 - Printers get paused, and jobs are not logged in PaperCut

Update: Full Support For Mac OS X 10.11 (El Capitan) was added in PaperCut version 15.2. If possible, please upgrade to version 15.2+ as it does not require any additional steps.

Note: This applies to a Primary or Secondary server installation where the PaperCut Print Provider is running to monitor print queues - not on every workstation, unless the PaperCut Print Provider is installed there too

The latest version of Mac OSX (10.11 - otherwise known as ‘El Capitan’) now includes CUPS version 2.1. When upgrading from previous versions of OSX, some of the CUPS config files will get re-written. Symptoms of the issue include filter errors appearing in the Print queue window on the Mac, and the print queues will go into a paused state.

Solution:

If you’re running PaperCut version 14.3 or above, simply re-run the Control Printer Monitoring.command - which will ask you if you want to update your CUPS sandboxing settings. Type ‘y’ and Enter. Once this is done, printing should work again.



macOS 10.10 (Yosemite)

NOTE: MacOS Server has been end of life as of 1st February 2018. See the link over here to our End of Life Policy

Printers get paused when using 10.10, and jobs are not logged in PaperCut (Resolved in 14.3.29819)

Note: This applies to a Primary or Secondary server installation where the PaperCut Print Provider is running to monitor print queues - not on every workstation, unless the PaperCut Print Provider is installed there too

The latest version of Mac OSX (10.10 - otherwise known as ‘Yosemite’) now includes CUPS version 2.0. The implementation includes tighter restrictions around access to the printing subsystem - also known as Sandboxing. We have found that these restrictions mean that PaperCut no longer has the access it needs to be able to control and monitor your print jobs. Symptoms include filter errors appearing in the Print queue window on the Mac, and the print queues will go into a paused state.

We have worked on a temporary solution for customers wanting to use 10.10 immediately. We hope to have a more refined solution in a future release of PaperCut, so that these manual workarounds won’t have to be used.

To get PaperCut working with Mac OS 10.10 in the interim, you’ll need to disable sandboxing. Edit the file /etc/cups/cups-files.conf to include the new line ‘Sandboxing Relaxed’. Then restart CUPS for this to take effect.

You can use the two commands below (copy and paste into the ‘Terminal’ application in Applications → Utilities → Terminal.app). You’ll be asked for your admin password after the first command is entered:

NOTE: DO NOT RUN THIS ON A MACHINE RUNNING MAC OS 10.9 OR BELOW

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

You should then find that printing and monitoring of your jobs through CUPS works as before.

For those who are interested in the behind-the-scenes details, there is a temporary fix for this in 14.3 - the behavior of the installation on Mac OS 10.10 changes with 14.3 in that by default the installation will complete without enabling Printers for monitoring in PaperCut.

If you are doing an install on 10.10 with 14.3, you’ll need to run the Control Printer Monitoring.command as detailed on the Enabling Printers on a Mac article. When you run this script on 10.10, it will also detect if Sandboxing is enabled in CUPS, and will offer to disable it for you to enable PaperCut integration.

This avoids the need to perform the steps above manually

iOS-advertised Printers are not visible from iOS devices

(Resolved in 14.3.29819)

When performing a fresh install of 14.2 or below on Mac OS 10.10, printers will not be advertised to iOS devices. This has been resolved in 14.3.

Note that this only applies to the PaperCut iOS print advertiser as detailed on the iOS Printing page. If you’re seeing this issue on any other version of Mac OS, please check the iOS Common Printing Questions article - particularly the section “Q. My printers don’t show up on the iOS devices when selecting a printer.”

Mail Drop

With Mac OSX 10.10, Apple have introduced Maildrop. This functionality allows people to email large documents (which would normally be rejected by email systems as too large). As the Apple documentation explains - when using Apple’s default Mail application, when someone attaches a document that is normally too large to email, it will create an iCloud link to the document and seamlessly upload it in the background.

Recipients who use Mail on Mac OSX 10.10 will see the attachment as a regular attachment (in the background it is downloading it for the user). Other non-iCloud or non-Apple-Mail users will see a link to the document where they can download it.

Currently PaperCut’s Email to Print feature will not recognize these iCloud links, so users who have sent large documents through Apple’s Mail program will get a return message saying: “Your Email to Print job was received, but no attachments were found. Please ensure you have attached a document and try again.”

In this situation, the only workaround would be to use a different mail client, or to uncheck the ‘Send large attachments with Mail Drop’ check box under Mail → Preferences → Accounts → Advanced, so that attachments are sent in the normal way.



macOS 10.9 (Mavericks)

Apple Mac OS 10.9 update causes PaperCut’s Application Server to be unresponsive (Resolved in PaperCut 13.5 Build 24862)

The recent release of Mavericks 10.9 for Mac OS has caused PaperCut to become unresponsive and unaccessible. This was identified as a priority issue. Our development team have already developed a fix for this issue, and is due to be released in the next minor release of PaperCut. Please do not update to Mavericks until our Release History indicates a new build for Mavericks 10.9.

If you have already installed the Mavericks update for Mac OS, there are two steps you can choose to run through, depending on what you would like to do. Both fixes have been confirmed working by PaperCut internally, as well as customer feedback.

  • Java update - A Java update can be manually downloaded that has been confirmed by customers to fix this issue and should be downloaded immediately if you have already updated your Mac OS to 10.9
  • PaperCut update - A PaperCut update can be downloaded and installed over your previous installation of PaperCut, which includes the future built-in changes for Mac OS 10.9 Mavericks.

Java update

A manual update can be run on Mavericks that has been confirmed to remedy this issue. The update is available here. Once this has been installed, please restart the PaperCut Application Server services.

PaperCut update

You may also wish to update your PaperCut installation to a build fixing this issue. Any future builds of PaperCut will have this fix implemented by default. Before downloading and installing this update, please ensure that you are licensed for version 13 of PaperCut. This can be checked on the About tab of your current PaperCut installation.

If you are unsure whether you are licensed, or cannot access the About tab to check this information, you can reach out to us via (http://support.papercut.com) including your company name, along with attaching your current PaperCut license. The license file can be found in Applications\PaperCut NG\Server\ and is called application.license.

Please make sure you follow the recommended upgrade procedure, outlined here.

Cause of the issue

The issue described is brought on after changes were made to the way Mac OS X bundled Java within their operating system. All previous versions of Mac OS X had included Java dependencies, but were removed in 10.9 Mavericks.



macOS 10.6.8 (Snow Leopard)

CUPS backends failing in 10.6.8

Changed line 190 from:

Problems printing landscape formatted pdf pages since 10.6.5

to:

Problems printing landscape formatted pdf pages since 10.6.5

Changed line 197 from:

Keywords: problems bugs

to:

Keywords: problems bugs

Changed lines 1-2 from:

(:title Known Printing Issues on Mac OS X Title:)

to:

(:title Known Printing Issues on Mac OS X :)

September 02, 2011, at 07:36 AM by tim - talk about mac issues separately for printing
Added lines 1-23:

(:title Known Printing Issues on Mac OS X Title:)

Below are a list of known issues which have been noticed on various releases of Mac OS X which affect printing but are not directly caused by PaperCut.

CUPS backends failing in 10.6.8

There have been reports for some people about printing failing on Mac OS 10.6.8 which is independent of PaperCut. The symptoms relate to one of the CUPS backends failing and potentially causing printing to pause. This has been tracked back to a problem with the CUPS backends of dnssd, ipp, lpd, and socket. An article discussing this can be found here. It references a program for backing up and copying over the old CUPS backends in order to fix the problem.

Problems printing landscape formatted pdf pages since 10.6.5

There have been a number of cases where landscaped pdf documents fail to be printed in landscape format and become truncated in portrait printouts. A discussion about this can be found here.


Keywords: problems bugs

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on November 13, 2019, at 12:27 AM
Printable View   |   Article History   |   Edit Article