Multiple Printing Regressions in Solaris 10 Kernel Patches 127127-11 and 127128-11

---

Multiple Printing Regressions in Solaris 10 Kernel Patches 127127-11 and 127128-11

1. Impact

Solaris 10 kernel patches 127127-11 (SPARC platform) or 127128-11 (x86 platform) introduce multiple printing regressions as listed below:

6715450 - 'lp -P m-' no longer prints pages for range 'm' until end of file.

6718897 - lpstat(1) output is missing information for Connection, Printer types, PPD, Character sets and Default Page Size.

6724904 - lpr(1B) -r and -s options are now mutually exclusive and attempting to use the options together generates a usage error.

6699182 - cancel(1) no longer works as expected when trying to cancel the following:

6729885 - When at least one print server is unreachable or not accepting connections, submission of print jobs may cause 'lpd-port' to hang, causing all print jobs to affected and unaffected print servers to be impacted.

6735837 - printmgr(1M) no longer displays the description for printers in the printer administration overview window.

6694850 - Issues with the list_remove() function in libpapi(3LIB) causes lists to be freed more than once resulting in a segmentation fault.

6698648 - 'lp -P <start>-<end>' no longer prints pages in the given range; instead, all pages of a given document will be printed.

6698649 - After resuming a held print job using 'lp -H resume', calling lp(1) -H hold will fail to place the job on hold.

6698650 - Priority order of 'lp -q' has been reversed.  'lp -q 0' should assign a print request the highest priority and 'lp -q 39' should assign the request the lowest priority. Patch 127127/127128-11 reverses this order causing 39 to be the highest priority and 0 to be the lowest.

6704910 - Options set for print requests, set via 'lp -o <option name>' are no longer being honored by the printing system.

6180823 - When banner printing is disabled for a printer using lpadmin(1M), printmgr(1M) incorrectly displays "Always print banner" regardless of the entry in the print database.

6708442 - Location of printing PPD files have changed causing printmgr(1M) to display a blank error message whenever the "New Attached Printer" window is closed.

6667354 - The changed location of printing PPD files causes printmgr(1M) to display an error when any modification or addition is actioned

6689188 - printmgr(1M) shows incorrect information for a given printer. The fields affected are:


The printing system performs correctly as specified by the print database, but the printmgr(1M) display does not reflect the correct values.

6707986 - Using lpset(1M) to add a print queue to an LDAP repository causes print requests targeting the new queue to fail. lpset(1M) does not add printer-uri data in a format that is compatible with the libpapi(3LIB) support for printer/service endpoint information.

Note the information for the following bugs has been moved to a new secondary Sun Alert for this printing regression issue: 6699689, 6740381, 6699255, 6720586, 6724477, 6737146  Please refer to this new new secondary Sun Alert 247386 for these BugIDs and more BugIDs relating to this printing issue.

2. Contributing Factors

These issues can occur in the following releases:

SPARC Platform:

• Solaris 10 with patch 127127-11
• OpenSolaris based upon builds snv_44 through snv_99
  

x86 Platform:

• Solaris 10 with patch 127128-11
• OpenSolaris based upon builds snv_44 through snv_99

Note: OpenSolaris is not affected by 6708442

OpenSolaris distributions may include additional bug fixes above and beyond the build from which it was derived. The base build can be derived as follows:

$ uname -v
snv_86

3. Symptoms

The symptoms of each issue are as listed below:

6715450 - When submitting a request with a page range, all pages of the document will be printed.

6718897 - 'lpstat -o <queue>' will return blank fields for Printer types, PPD, Connection, Character Sets and Default Page Size even when this fields have been populated with information.

6724904 - lpr(1B) will report the following usage error:
6729885 - Print requests to remote printers will be seen to hang.

6735837 - printmgr(1M) will show blank descriptions in the printer overview window even when printer description fields have been populated.

6694850 - The stack trace from the core file will be similar to the following:

fedc246c papiAttributeValuesFree (deadbeef, deadbeef) + 1c
fedc24d6 papiAttributeFree (8067a90) + 3a
fedc250f papiAttributeListFree (806da98) + 27
fede4e68 papiServiceDestroy (8068430) + 5c

6698648 - All pages will be printed even if a valid page range has been supplied.

6698649 - After applying a hold to a print request, lpstat(1) will not show the request as being held.

6698650 - Applying a priority of 39 will result in the request being moved to the top of the print queue. Applying a priority of 0 will result in the request being moved to the end of the queue. This behavior can be observed via lpstat(1).

6704910 - Examining /var/spool/lp/logs/requests will show the request as having a field: "Ui=false" which is not understood by the print server.  A mail will also be received by the user containing this information.

6180823 - printmgr(1M) will always show the banner option as:


regardless of the setting applied.

6667354 - printmgr(1M) will display a popup error message containing "java.lang.NullPointerException" when closing the printer addition/modification windows, whether or not any printer settings were modified/added.

6689188 - After modifying a printer via printmgr(1M), viewing the details of the printer again using printmgr(1M) will show no changes having been made. File Contents, Notification and Printer Type will still have the previous values.

6699182 - 'cancel(1) -u <user>' will result in all printers being purged of all jobs, regardless of whom owns them.
'cancel -u <user> <printer>' will result in the supplied printer being purged of all jobs - again, regardless of the owner.

6708442 - printmgr(1M) will show a blank popup error message when closing the add/modify printer window.

6707986 - After using lpset(1M) job submission via lp(1) will produce an error message similar to the following:

<queue>: failed to commit job (<job id>): unknown destination

4. Workaround

Removing the affected patches 127127-11 (SPARC platform) or 127128-11 (x86 platform) will resolve these printing issues. However, these patches fix certain security issues which are not resolved by any other patch, and as such, this course of action is not recommended.

5. Resolution

These issues are addressed in the following releases:

SPARC Platform:

Solaris 10 with:

• patch 138112-01 or later (for 6180823, 6667354, 6689188)
• patch 138116-01 or later (for 6698648, 6698649, 6698650, 6704910)
• patch 138118-01 or later (for 6699182)
• patch 138120-01 or later (for 6708442)
• patch 138627-02 or later (for 6694850)
• patch 139487-01 or later (for 6724904)
• patch 138870-01 or later (for 6707986)
• patch 138627-03 or later (for 6715450)
• patch 138848-02 or later (for 6718897)
• patch 139390-01 or later (for 6735837)
• patch 140192-01 or later (for 6729885)
• OpenSolaris based upon builds snv_100 or later

x86 Platform:

Solaris 10 with:

• patch 138113-01 or later (for 6180823, 6667354, 6689188)
• patch 138117-01 or later (for 6698648, 6698649, 6698650, 6704910)
• patch 138119-01 or later (for 6699182)
• patch 138121-01 or later (for 6708442)
• patch 138628-02 or later (for 6694850)
• patch 139488-01 or later (for 6724904)
• patch 138871-01 or later (for 6707986)
• patch 138628-03 or later (for 6715450)
• patch 138849-02 or later (for 6718897)
• patch 139391-01 or later (for 6735837)
• patch 140193-01 or later (for 6729885)
• OpenSolaris based upon builds snv_100 or later

Note the current/latest patches that that will deliver all the above fixes are:

• SPARC - 138848-02 138627-03 138411-01 138858-01 139487-01 138870-01, 139390-01, 140192-01
•  x86   - 138849-02 138628-03 138412-01 138859-01 139488-01 138871-01, 139391-01 140193-01

Note that it is advisable that customers install these patches since this is the patch baseline for relief available for the issues documented in Sun Alert 247386.

This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.


Modification History

10-Sep-2008: Correction to Resolution section for SPARC patches
16-Sep-2008: Clarification for OpenSolaris versions listed in Contributing Factors
09-Dec-2008: Updated BugIDs, Impact, Contributing Factors, Workaround and Resolution sections
12-Dec-2008: Updated Contributing Factors and Resolution sections, now Resolved
19-Dec-2008: Republished

Attachments

This solution has no attachment