Patch-ID# 101362-38 Keywords: xsun, server, jumbo, patch Synopsis: OpenWindows 3.3: Server (Xsun) Jumbo Patch Date: May/09/95 Solaris Release: 2.3 SunOS Release: 5.3 Unbundled Product: OpenWindows Unbundled Release: 3.3 Relevant Architectures: sparc BugId's fixed with this patch: 1141315 1142771 1146111 1141375 1144461 1146088 1152001 1152769 1151914 1152944 1147430 1144743 1151315 1124764 1143469 1150198 1145096 1149675 1136010 1156204 1155735 1155459 1127452 1152183 1157391 1129822 1160954 1143823 1156204 1163461 1139622 1157309 1139673 1160924 1129184 1145180 1159294 1172227 1159297 1171660 1171816 1172825 1176147 1178297 1178838 1169371 1177198 1157278 1184905 1182946 1181295 1187491 1186502 1187859 1176797 1187859 Changes incorporated in this version: 1186139 Patches accumulated and obsoleted by this patch: 101307-01 101457-01 101687-01 101593-02 Patches which conflict with this patch: 101687-01 101262-22 101237-22 Patches required with this patch: Obsoleted by: Files included with this patch: /usr/openwin/bin/xhost /usr/openwin/bin/Xsun /usr/openwin/server/lib/libcfb.so.1 /usr/openwin/server/lib/libcfb16.so.1 /usr/openwin/server/lib/libcfb32.so.1 /usr/openwin/server/lib/libfont.so.1 /usr/openwin/server/lib/libmi.so.1 /usr/openwin/server/lib/libmpg.so.1 /usr/openwin/server/modules/ddxSUNWcg6.so.1 /usr/openwin/server/modules/ddxSUNWkbd.so.1 /usr/openwin/server/modules/ddxSUNWmouse.so.1 /usr/openwin/server/modules/ddxSUNWdials.so.1 /usr/openwin/server/modules/ddxSUNWdialsCompat.so.1 Problem Description: 1186139 OWN 3.3 Xsun server lost when enlarging image after printing Incorporated from patch 101362-37: 1186502 xfd displays incorrect morisawa scalable font after dps appl 1176797 CDE workspace tiling is way too slow on TGX+ 1187491 Partial fix to CAP_NOT_LAST attr. causes the server to crash 1157278 Console errors when adding extension device & parsing OWconfig 1182946 circles are rendered with square edges 1181295 OLIT 3.3 LED off if number of entered character more than max 1169371 GX+ draws garbage when moving double buffered window 1184905 icons get ghosted after install patch 101362-27 1177198 Xsun server continuously polling, reading bogus file descriptor 1169371 GX+ draws garbage when moving double buffered window 1178838 F3 font appears on coordinates of incorrect position by using DPS 1178297 Xsun crashes when using sundials in Unigraphics 1176147 XtSetValues call with valid parameters causes core dump (in miUnion) 1172825 XDrawString is very slow if large (34) point sizes are used. 1171816 XTEST 2.2 patch compatible with previous XDM patch needed 1171660 Xsun crashes during ConfigureWindow Request (CTE 9965) 1159297 Xsun hang on ZX/SX when drawing large circles with XDrawArc()(CTE 10266) The patch 101687-01 has been integrated into this jumbo patch (CTE 10266) 1172227 Xsun suddenly dumps core when cursor pointer moves at bottom right corner The following was fixed by backing out the fix for BugID 1129184: 1155459 Type4 German keyboard goes in/out strange state (s494_prealpha7) 1156204 Extension input devices cannot become the core pointer 1155735 Xsun multibuffering fails with GXplus; Lines drawn outside window 1136010 console prompt from PROM left white on white by PutBanner 1144743 Xsun core dumped while zoom/preview of imagetool of gif on C2+ cg14 1151315 Xsun core dump after DnD 1124764 after a period of time, can't run any dps apps on s1093_pr1 server 1143469 Sometimes, cannot run pageview at all 1150198 Running version of Emacs kills Xserver under Solaris 1145096 xsun dumps core 1149675 xsun: Server hangs during CDE test execution 1152769 Xsun refuses connection when many procs connect simultaneously 1151914 Xsun server goes into infinite loop running Xlib app using setitmer 1152944 Xsun DGA does not wrap the GCops correctly 1147430 mwm on an IPX causes wide bands on root & color change 1152001 OpenWindows 3.3 fails to pop HWC module on exit 1141315 Xsun grew to 100MB by showing second page of helpviewer in Japanese 1142771 Kanji PostScript rendering is 8 times slower than xnews 1146111 Xsun goes into infinite loop when connected to a font server, has to be killed (triggered by wabi) 1146088 lines can render outside of color windows on CG8 & CG3, may crash server 1141375 AUXDEV server extension does not work in SunOS 2.3 (breaks SUNPC) 1144461 Code ok on OW3.2/OS5.2 causes OpenWindows to exit on OW3.3/OS5.3 1127452 Japanese minm14 and minb14 fonts look bad in s1093 1152183 mpg prevents 24 bit pixmaps from being freed 1157391 xfd show wrong font image if used the morisawa scalable fonts 1129822 V3.3 server putting out null connectionType XDMCP record 1160954 TurboGXPlus fb has problem displaying right colors 1143823 XSun with Morisawa F3 font returns wrong ascent and descent 1156204 Extension input devices cannot become the core pointer in Solaris 2.3 1163461 XGetFeedbackControl, XChangeFeedbackControl produce X errors 1139622 - xhost does not work with a decnet node name 1157309 - xserver denies access from VAXhosts which uses host::notation 1139673 keyrepeat appeared to get stuck. 1160924 XGL/XIL apps "freeze" when running multiple apps. 1129184 Need support for new Kana LED on Japanese Hobo keyboard. 1145180 in ja locale, VERTICALOFFSET in kanji.trans does not work 1159294 Japanese DPS shows vertical glyphs on incorrect position 1187859 Filling with fillStyle == FillTiled is slower on GX+ when tile 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: ----------------------------- Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing:
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Installpatch will backout the patch
to leave the system in its pre-patched state. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Error message:
Pkgadd of package failed with error code .
Will not backout patch...patch re-installation.
Warning: The system may be in an unstable state!
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
the patch packages failed. Installpatch will NOT backout the
patch. You may manually backout the patch using backoutpatch,
then re-apply the entire patch. Look in the log file for the
reason pkgadd failed. 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.
Message:
Re-installing Patch.
Explanation: The patch has already been applied, but there is
at least one package in the patch that could be added. For
example, if you applied a patch that had both Openwindows and
Answerbook components, but your system did not have Answerbook
installed, the Answerbook parts of the patch would not have
been applied. If, at a later time, you pkgadd Answerbook, you
could re-apply the patch, and the Answerbook components of the
patch would be applied to the system.
Message:
Installpatch Interrupted.
Installpatch is terminating.
Explanation: Installpatch was interrupted during execution
(usually through pressing ^C). Installpatch will clean up
its working files and exit.
Message:
Installpatch Interrupted.
Backing out Patch...
Explanation: Installpatch was interrupted during execution
(usually through pressing ^C). Installpatch will clean up
its working files, backout the patch, and exit.
Patch Backout Errors:
---------------------
Error message:
prebackout patch exited with return code .
Backoutpatch exiting.
Explanation and corrective action: the prebackout script
supplied with the patch exited with a return code other
than 0. Generate a script trace of backoutpatch to determine
why the prebackout script failed. Correct the reason for
failure, and re-execute backoutpatch.
Error message:
postbackout patch exited with return code .
Backoutpatch exiting."
Explanation and corrective action: the postbackout script
supplied with the patch exited with a return code other than
0. Look at the postbackout script to determine why it failed.
Correct the failure and, if necessary, RE-EXECUTE THE
POSTBACKOUT SCRIPT ONLY.
Error message:
Only one service may be defined.
Explanation and corrective action: You have attempted to specify
more than one service from which to backout a patch. Different
services must have their patches backed out with different
invocations of backoutpatch.
Error message:
The -S and -R arguments are mutually exclusive.
Explanation and recommended action: You have specified both a
non-native service to backout, and a package installation root.
These two arguments are mutually exclusive. If backing out a
patch from a non-native usr partition, the -S option should be
used. If backing out a patch from a client's root
partition (either native or non-native), the -R option
should be used.
Error message:
The service cannot be found on this system.
Explanation and recommended action: You have specified a non-
native service from which to backout a patch, but the
specified service is not installed on your system. Correctly
specify the service when backing out the patch.
Error message:
Only one rootdir may be defined.
Explanation and recommended action: You have specified more than
one package install root using the -R option. The -R option
may be used only once per invocation of backoutpatch.
Error message:
The directory cannot be found on this system.
Explanation and recommended action: You have specified a
directory using the -R option which is either not mounted,
or does not exist on your system. Verify the directory name
and re-backout the patch.
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: You have attempted to backout
a patch that is not applied to this system. If you must
restore previous versions of patched files, you may have to
restore the original files from the initial installation CD.
Error message:
Patch has not been successfully applied to this system.
Will remove directory
Explanation and recommended action: You have attempted to back
out a patch that is not applied to this system. While the
patch has not been applied, a residual
/var/sadm/patch/ (perhaps from an unsuccessful
installpatch) directory still exists. The patch cannot be
backed out. If you must restore old versions of the patched
files, you may have to restore them from the initial
installation CD.
Error message:
This patch was obsoleted by patch .
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: You are attempting to backout
patches out of order. Patches should never be backed-out out
of sequence. This could undermine the integrity of the more
current patch.
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, cpio