Patch-ID# 101656-09 Keywords: Pipe Japanese core xnews server setdash MS PowerPoint Acrobat FrameMaker. Synopsis: NeWSprint 2.5 Rev B: xnews server jumbo patch. Date: Jun/28/96 Solaris Release: 2.1, 2.2, 2.3, 2.4, 2.5 SunOS Release: 5.1, 5.2, 5.3, 5.4, 5.5 Unbundled Product: NeWSprint, Japanese NeWSprint Unbundled Release: 2.5 Rev B, J2.5 Rev B Relevant Architectures: sun4c, sun4m, sun4d BugId's fixed with this patch: 1135751 1137474 1153896 1155730 1170296 1174249 1179508 1180975 1176530 1178920 1183419 1191585 1193446 1196477 1196538 1206787 1226046 1228478 1229476 1229514 1236257 1240574 1241992 1243756 Changes incorporated in this version: 1229476 1229514 1236257 1240574 1241992 1243756 Patches accumulated and obsoleted by this patch: 101232-02 Patches which conflict with this patch: Patches required with this patch: 101655-05 Obsoleted by: Files included with this patch: /opt/NeWSprint/small_openwin/bin/xnews /opt/NeWSprint/np/nps/operator-list.ps /opt/NeWSprint/np/nps/coverups.ps /opt/NeWSprint/np/nps/prt.ps /opt/NeWSprint/np/nps/ncimg.ps /opt/NeWSprint/pl.sun4/C/include/tray1.ps /opt/NeWSprint/pl.sun4/C/include/tray2.ps Problem Description: 1229476 xnews prints to incorrect position (on 2nd job) if banner page turned off 1229514 FrameMaker file cannot print after first job if banner page turned off 1236257 JNP2.5B: can't select the tray on SPARCprinterII with pl command 1240574 Framemaker docs will print once, then hang newsprint 2.5 rev b w/banner disabled 1241992 NeWSprint will not print certain postscript files to NeWSprinter 20, SPARCprinter II 1243756 PostScript output to NeWSprinter20 on Solaris 2.5 fails (from 101656-08) 1226046 NeWSprint cannot print postscript file with 0 width or 0 length image size. 1228478 JNP2.5B: cannot print color data (/imagemask load of user-defd pattern) (from 101656-07) 1206787 core dump when default tray has nonletter size of paper. (from 101656-06) 1174249 Mac application PowerPoint cannot print to our printers. 1176530 Text are printed incorrectly in color PS file. 1178920 missing characters on Globalview files. 1183419 command charpath doesn't create outline charcter correctly. 1191585 Characters are dropped when printing from Frame and Interleaf. 1193446 Japanese NeWSprint can not print out the files which are produced by MS-Windows 1196477 xnews dumps core. 1196538 Not able to print postscript file generated by Adobe Acrobat (from 101656-05) 1179508 Sample file can't be print at correct position. 1180975 NeWSprint 2.2, sometimes occured "XNeWS: internal error detected (SIGSEGV)". (from 101656-04) 1170296 A post-script file from MS PowerPoint apps does not print correctly. (from 101656-03) 1155730 A color postscript file failed to print for NeWSprinterCL+ printer. (from 101656-02) 1135751 NeWSprint 2.5 RevB xnews server is core dumped, and pipe is broken. (from 101656-01) 1153896 NeWSprint 2.5 RevB Setdash does not work correctly. (from 101232-02) 1137474 F3 type fonts were rendered backwards due to the bug in inverse ion formula. The patch fixes this problem. Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- 1. Log in as superuser (root): # su Password: 2. Disable the printing server, shutdown lp system: # lpshut 3. find the NeWSprint's server and kill it. # ps -aef |grep nodev server_id # kill -9 server_id 4. Apply the patch by typing: #
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Any previously installed packages
in the patch should have been removed. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Patch Installation Messages:
---------------------------
Note: the messages listed below are not necessarily considered errors
as indicated in the explanations given. These messages are, however,
recorded in the patch installation log for diagnostic reference.
Message:
Package not patched:
PKG=SUNxxxx
Original package not installed
Explanation: One of the components of the patch would have patched a
package that is not installed on your system. This is not
necessarily an error. A Patch may fix a related bug for several
packages. Example: suppose a patch fixes a bug in both the
online-backup and fddi packages. If you had online-backup installed
but didn't have fddi installed, you would get the message
Package not patched:
PKG=SUNWbf
Original package not installed
This message only indicates an error if you thought the package
was installed on your system. If this is the case, take the
necessary action to install the package, backout the patch (if
it installed other packages) and re-install the patch.
Message:
Package not patched:
PKG=SUNxxx
ARCH=xxxxxxx
VERSION=xxxxxxx
Architecture mismatch
Explanation: One of the components of the patch would have patched a
package for an architecture different from your system. This is not
necessarily an error. Any patch to one of the architecture specific
packages may contain one element for each of the possible
architectures. For example, Assume you are running on a sun4m. If
you were to install a patch to package SUNWcar, you would see the
following (or similar) messages:
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4c
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4d
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4e
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
The only time these messages indicate an error condition
is if installpatch does not correctly recognize your architecture.
Message:
Package not patched:
PKG=SUNxxxx
ARCH=xxxx
VERSION=xxxxxxx
Version mismatch
Explanation: The version of software to which the patch is applied is
not installed on your system. For example, if you were running Solaris
5.3, and you tried to install a patch against Solaris 5.2, you would
see the following (or similar) message:
Package not patched:
PKG=SUNWcsu
ARCH=sparc
VERSION=10.0.2
Version mismatch
This message does not necessarily indicate an error. If
the version mismatch was for a package you needed patched, either
get the correct patch version or install the correct package version.
Then backout the patch (if necessary) and re-apply.
Patch Backout Errors:
---------------------
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: The user has attempted to back
out a patch that was never applied to this system. It is
possible that the patch was applied, but that the patch
directory /var/sadm/patch/ was deleted somehow.
If this is the case, the patch cannot be backed out. The
user may have to restore the original files from the
initial installation CD.
Error message:
This patch was obsoleted by patch $1.
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: The obsoleted contents of an
older patch rev that apparently still exists under /var/sadm/patch
should never be restored out of sequence. This could undermine
the integrity of the more current patch rev installed and the
restoration of the files it has saved.
Error message:
Patch was installed without backing up the original
files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used. The
original files can only be recovered from the original
installation CD.
Error message:
pkgrm of package failed return code .
See /var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file for the reason for
failure. Correct the problem and run the backout script again.
Error message:
Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See instructions above for
applying patches to a client.
A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
could affect the reliability of installpatch or backoutpatch
which uses package utilities to install and backout the patch
package. It is recommended that any patch that fixes package
utility problems be reviewed and, if necessary, applied before
other patches are applied. Such existing patches are:
100901 Solaris 2.1
101122 Solaris 2.2
101331 Solaris 2.3
SEE ALSO
pkgadd, pkgchk, pkgrm, pkginfo, showrev