Patch-ID# 101377-20 Keywords: motif, ixi, jumbo, patch, 1.2.2, libXm.a Synopsis: Motif 1.2.2: libXm Jumbo Patch Date: Aug/19/94 Solaris Release: 2.2, 2.3 SunOS Release: 5.2, 5.3 Unbundled Product: Motif Unbundled Release: 1.2.2 Relevant Architectures: sparc BugId's fixed with this patch: 1147146 1144787 1150952 1152786 1153027 1154491 1155734 1141680 1142974 1146940 1149041 1157214 1138684 1148471 1156458 1158943 1160390 1159259 1153004 1159062 1161062 1158959 1161081 1162433 1162436 1163680 1160458 1156629 1160158 1165903 1163938 1167476 1167222 1169241 1162422 1169241 1171150 1171951 1169662 1172467 1172072 1173192 Changes incorporated in this version: 1173192 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Solaris 2.2 - 101084-03 Solaris 2.3 - none Obsoleted by: Files included with this patch: /opt/SUNWmotif/reloc/SUNWmotif/lib/libXm.a /opt/SUNWmotif/reloc/SUNWmotif/lib/libXm.so.2 /opt/SUNWmotif/reloc/SUNWmotif/share/include/Xm/DisplayP.h /opt/SUNWmotif/reloc/SUNWmotif/share/include/Xm/VirtKeysP.h Problem Description: Bug Id : -------- 1147146 unmanaging FormDialog widget after a child has been destroyed causes segv 1144787 CompareNodesVert gives incorrect result when sorting widgets 1150952 XtMakeGeometryRequest fails to raise or lower windows in Motif application 1152786 Form widgets clipped to scroll widgets fail 1153027 Character cell size is calculated incorrectly when XCreateFontSet() is used 1154491 SEGV of motif when doing a XmTextSetString in a popup 1155734 textwidget callback dumps core when setting XmNmodifyVerifyCallback 1141680 Installing a drop-site on an application shell causes a SEGV in XmDropSiteRegist 1142974 dropFinishCallbackStruct not initialized correctly 1146940 Setting XmNpositionIndex of a RowColumn child fails (SEGV) 1149041 Motif listbox widget changes color to black 1157214 uninitialized memory read causes menu geometry problems 1159062 Seg fault after destroying cascade with shared menupane. 1160458 library differences between original FCS and SDK Motif 1138684 Cannot input numeral even if NumLock key is engaged. 1148471 Customer's application core dumps when using a FormDialog widget 1156458 XmNunitType resource in XmForm widget is broken 1158943 grabs are messed up in modal dialogs 1160390 return in XmList after calling XmListDeselectAllItems causes crash 1159259 Motif Widget Binary Compatibility mechanism broken 1153004 Failure to escape from menubar using F10/ESC 1161062 The baseline of font isn't displayed properly when using XmFONT_IS_FONTSET. 1158959 XmCreateSimpleOptionMenu crashes 1161081 BadFont Xlib Errors when connecting to more than one display using 1162433 XmNwidth of button's label is short when using XmStringConcat() 1162436 On Solaris2.3,the baseline of font isn't displayed properly 1163680 freed memory read in motif 1156629 can't create above 71 XmText Wiget when setting XtSetLanguageProc() 1160158 status message is incorrectly located 1165903 Heap corruption after calling XmDropSiteRegister 1163938 libXm.so itself needs to be compile with -lXt and -lX11 1167476 functional difference of XmNhorizontalSpacing on Form widget from OSF motif 1167222 Form resource with XmNleftWidget=NULL produces warning message 1169241 Bottom of label string not drawn correctly when applying Patch#101377-11 1162422 XmNborderWidth isn't set when be applyed patchid#101377-06 1171150 Pressing F10 on help cascade button causes core dump 1171951 Motif 1.2.2 : overstrike problem in text widget 1169662 Drag operation within text widget causes grabbing keyboard on SDK motif1.2.2 1172467 Motif 1.2.2 Can not gray out ListWidget by setting False to XmNsensitive 1172072 can't change the shape of ToggleButton by XtSetValues() 1173192 Motif 1.2.2 : setting the default button dumps core 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: ----------------------------- None. 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