PaperCut KB | Known Issues with Recent Releases

Printable View Home » Main » Known Issues with Recent Releases

Known Issues with Recent Releases

This page lists known issues or bugs with the most recent releases. The aim is to arm administrators with information about problems in the current release and where possible mention workarounds or methods to mitigate the issues.

Version 10.1 build 9816

Running a PDF or HTML report may cause an error if running PaperCut on a Linux primary server without the MS fonts pack installed. It was not intended that installing the MS fonts pack be a requirement, so in the next release this error will no longer be raised. In the meantime installing the MS fonts pack for your distribution will suppress the error. On Debian based distributions the relevant package is called ttf-mscorefonts-installer, on SuSE it is fetchmsttfonts, for RedHat users you can build from source available here: http://corefonts.sourceforge.net/.

Version 10.1 build 9802

When creating a new scheduled report users may experience an error that stops the creation of the report. Upgrading to version 10.1 build 9816 or later will address this issue.

Version 10.0 build 9546

If the client software is started with the --minimized option and the account selection pop-up is enabled, in some rare situations the client may consume high CPU until the window is focused in the foreground. This issue only affects the Windows operating system. A patch is available if required. The alternate solution is to temporarily remove the start --minimized option.

Web Print users may experience issues when printing PDF files generated in Open Office that have a Title added to the document properties. To work around this issue the author of the PDF can deselect Display document title under File -> Export PDF -> User Interface when creating the PDF document.

PaperCut on Debian Linux (netbase 4.39-4.40)

A change in the above Debian version update breaks networking in many applications. The PaperCut application server may fail to start and/or fail to accept connections (i.e. cannot access the web interface). There is contention over whether the change is a bug or the right thing to do. More information and a workaround (set net.ipv6.bindv6only=0) are available in this Debian bug report:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560238

Version 9.X on Mac 10.6 and Linux running CUPS 1.4

A change in CUPS 1.4 will prevent PaperCut's pop-up authentication working. PaperCut has already addressed this issue in version 9.8.

Version 9.7 build 9159

There is a bug in "Printer environmental impact - summary" which prevents the report from running. A patch to fix this issue is available from PaperCut support.

Versions 9.5 and 9.6

There is a problem accessing the iPhone user web interface in these versions. This issue will be addressed in the next release.

Version 9.0 through 9.5

We've had some of our very large sites report stability problems when running PaperCut version 9.X prior to version 9.6.8855 on Windows 2003/8 servers. The symptoms include:

The server drops off the network for no explainable reason
Random network connection issues (e.g. file shares dropping off)
Errors about out of "non-paged pool memory" in the Windows Event Log

If any large sites are experiencing these problems should upgrade to the latest release (9.6.8855 or higher). Full details below:

PaperCut uses an embedded web server called Jetty. This is a popular open source embedded web server and is used by organizations including Google who use Jetty in Google App Engine. In PaperCut version 9, we enabled Jetty's support for asynchronous-IO (non-blocking IO). This increases PaperCut's scalability by removing the one-thread-per-connection limit. This change however has had the side affect of triggering stability problem on some servers running on very large networks. It seems that PaperCut (via Jetty) is triggering a memory leak in the Window TCP/IP stack and kernel - a leak in non-paged pooled memory. This leak causes unpredictable behavior in the OS in the networking area (i.e. connection problems) and can only be addressed by a server reboot. The memory is not released even when PaperCut is quit as the bug is at the operating system kernel level in the Windows TCP stack.

We have thousands of customers running PaperCut, and very few sites are affected. It's only an issue on Windows 2003/2008 running on large networks and may be related to a particular server configuration or network driver and/or combination. We have the team at Jetty working on this now. Jetty is an open source project so we've financially contributed to the developers so they can dedicate more time to this issue. The issue however is likely to be a Microsoft bug and it may not be possible to work around it so we will be reverting back to the old behavior for our next release. In 9.6 we've added a new configuration option that allows sites to revert back to the old I/O behavior if they are affected by the issue.

Thanks to the guys at University of Iowa and Miami Dade College for helping us and the Jetty team's assistance in tracking down this issue.

Version 9.6 build 8761

Sites using the web-print in "simple" mode may find that the web-print service stops if using 3rd party service monitoring tools. A patch for this issue is available from PaperCut support.

Web Print jobs submitted with a document name containing non-Latin (e.g. Chinese) letters may not print in some cases. This will be addressed in the next release. A patch can be arranged if required.

Version 9.5

Sites using Find Me Printing or printer load balancing may find that jobs are not redirected to the optimal queue under the following conditions:

if admin printer error notifications are disabled
if printers re-error (error, cleared, error again) within a few hours

Admin printer error notifications may also not be delivered for printers that re-error within a few hours.

This issue was addressed in version 9.6. The behavior may be improved on earlier versions by enabling admin printer error notifications via

Options -> Notifications -> System Notifications -> Notify when printers are in error.

Also if the printer name contains an ampersand (&), then the jobs may not be correctly redirected to this printer. This has also been fixed in 9.6.

Version 9.2 build 7214

This version contains a bug where the client's task tray icon will not display if the client is started with the --silent option. Sites running build 7214 that are experiencing this problem should look at upgrading to version 9.2 build 7345.

Version 9.0 build 7022

This release includes a problem for sites running PaperCut on Mac Servers that also use the Windows user client or release station. The Windows user client and release station includes a corrupt file that causes these to fail to start. NOTE: This does not affect the Mac client or release station. The problem is corrected in Version 9.1 build 7117.

Version 9.0 also contains a regression where some Postscript drivers would report incorrect page sizes. This issue has been addressed in Version 9.1 build 7117 or higher.

Version 8.5 build 6666

This release includes a bug in the scheduled email reports. Reports with selected parameter combinations may not deliver with the correct date range. The solution is to upgrade to build 6739 or higher.

Version 8.5 build 6595

This release contains a screen layout problem in IE 6 causing selected logo's to lay out incorrectly. The current solution is to upgrade to IE 7 or Firefox, or transition to build 6666 or higher.

Note: Full version and build number information is listed under the About page

See the release notes for information and a list of known issues with older releases not listed on this page:

The latest version is always available from the download pages:

PaperCut NG: http://www.papercut.com/products/ng/download/

PaperCut ChargeBack: http://www.papercut.com/products/chargeback/download/

Keywords: problems, bugs, hotfixes, release notes