Patch-ID# 101550-02 Keywords: xim, xlibi18n, asian, performance, language, session, XIC, textWideget Synopsis: OpenWindows 3.3: XIM fixes for Asian Solaris 2.3 Date: Apr/11/94 Solaris Release: 2.3 SunOS Release: 5.3 Unbundled Product: Unbundled Release: Relevant Architectures: sparc BugId's fixed with this patch: 1155249 1155715 1155842 1155712 1158237 1157346 1158853 1158864 1150547 1156327 1156897 1158840 1160667 1160584 1160586 1159289 1152195 Changes incorporated in this version: 1158237 1157346 1158853 1158864 1150547 1156327 1156897 1158840 1160667 1160584 1160586 1159289 Patches accumulated and obsoleted by this patch: 101550-01 Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: reloc/openwin/bin: htt reloc/openwin/lib/locale/common/xim: cm.so reloc/openwin/lib/locale/ja: XLIBI18N/xlibi18n.so.1 CT_Encoding reloc/openwin/lib/locale/ko: XLIBI18N/xlibi18n.so.1 CT_Encoding reloc/openwin/lib/locale/zh: XLIBI18N/xlibi18n.so.1 CT_Encoding reloc/openwin/lib/locale/zh_TW: XLIBI18N/xlibi18n.so.1 CT_Encoding reloc/usr/mle/ko: mle.so libmle.a Problem Description: 1155249 htt creates fontsets for every single XIC 1155715 htt takes more than 1 second for TextField widget creation 1155842 Korean language engine got a limit in the number of open sessions 1155712 user application and cmdtool hung in ximp 1158237 cmdtool hung up waiting Ximp reply 1157346 htt leaks memory when OLIT textFieldWidget is repeatedly created/destroyed 1158853 foreground color and background color are not reversed in the preedit string 1158864 OffTheSpot preedit is displayed on an incorrect position 1150547 Icon title do not get translated message from .mo file 1156327 rootwindow preedit strings are sometimes not drawn 1156897 In an XIMStatusNothing style client, status is on right side of rootwindow 1158840 status strings in the RootWindow is sometimes invisible 1160667 preedit window disappears when child window gave up input focus to parent 1160584 htt dumps core when applying after editing the property sheet 1160586 mailtool dumps core in XCreateIC() 1159289 OLIT client can't grab any event with displaying strange status 1152195 htt dumps core when setting "-preedit_style overTheSpot" 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: ----------------------------- Note: The following patch packages will be installed on your system when you apply this patch ... --------------------------------------------------------------------- If your system is a the following patch packages will be installed --------------------------------------------------------------------- Japanese Solaris 2.3 FCS SUNWawcom, SUNWjwrqd Korean Solaris 2.3 FCS SUNWawcom, SUNWkow, SUNWkleu Chinese/Taiwan Solaris 2.3 FCS SUNWawcom, SUNWhow Chinese/PRC Solaris 2.3 FCS SUNWawcom, SUNWcow 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. 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