Patch-ID# 101879-01 Keywords: XView binary compatibility Synopsis: OpenWindows 3.4: XView jumbo patch Date: Sep/15/94 Solaris Release: 2.4 SunOS Release: 5.4 Unbundled Product: OpenWindows Unbundled Release: 3.4 Relevant Architectures: sparc BugId's fixed with this patch: 1066919 1072832 1073167 1066366 1075863 1075950 1059597 1080579 1075124 1073246 1065873 1084865 1083436 1083405 1053515 1078467 1061299 1076560 1037992 1044411 1055172 1068828 1077164 1091601 1093039 1049703 1087337 1074553 1053036 1053292 1030878 1020408 1097384 1076907 1043723 1101846 1103579 1105512 1106032 1098466 1106525 1093908 1067716 1109382 1108767 1113021 1110227 1109875 1114662 1111308 1114561 1065350 1067367 1115954 1053622 1109875 1122244 1122239 1122353 1072252 1117789 1071584 1124324 1066669 1098379 1131411 1129722 1140264 1134887 1140806 1136974 1139167 1142387 1047558 1140250 1148561 1148724 1110936 1149528 1148277 1145729 1161640 1160672 1161637 1161924 1164206 1164512 1137807 1165614 Changes incorporated in this version: 1165614 Patches accumulated and obsoleted by this patch: 101768-01 Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /usr/4lib/libxview.so.3.65 Problem Description: 1165614 Read only fields are still Drag&Drop targets in xview. This patched fixes the list of bugs referenced below. 1072832 App may hang server if notify proc takes a long time 1073167 Pressing help in scrollbar can core dump xview applications 1066366 Typing ^B when cursor at top of text window goes into infinite scroll loop 1075863 XView doesn't display menus when the # of items reaches limit of 1 column 1075950 V3 slow to start/exit an app as compared to V2 1059597 check box choices don't display the correct color until refreshed 1080579 OW3.0 cmdtool doesn't echo characters if raw mode selected 1075124 Textsw line spacing doesn't meet TUV requirements 1073246 Panel text items send a delete request after only receiving a filename 1065873 PANEL_VALUE_DISPLAY_LENGTH in text item does not work for values less than 4 1084865 MENU_NROWS doesn't clamp menu to specified number of rows 1083436 menu_show: Menu too large for screen 1083405 xv_destroy frame memory leak 1053515 Memory leak in PANEL_CHOICE items 1078467 xview3.0 (SCROLLABLE_PANEL,PANEL) program runs much slower than xview2.0 1061299 Textsw leaks memory after textsw_reset() 1076560 added attribute SCROLLBAR_PERCENT_OF_DRAG_REPAINTS to be OL Level 2 compliant with scrollbar dragging 1037992 Suspending a cmdtool with control-Z kills it 1044411 Text Subwindow does not paint color correctly 1055172 textsw doesn't work with LARGE files 1068828 cmdtool leaks memory when continuously displaying data 1077164 cmdtool L2/AGAIN key displays unechoed characters 1091601 cmdtool feature has potential for revealing passwords 1093039 XView jumbo patch 100452-10 breaks textsw package 1049703 "META" character is not recognized in shelltool & cmdtool 1087337 Textsw leaks memory after textsw_reset() 1074553 selection service cut/paste drag/drop is glacial 1053036 xv_set(textsw, XV_FONT, xvfont, NULL) doesn't work anymore 1053292 shelltool doesn't report correct screen size 1030878 carriage return gets turned into a linefeed in a TERMSW 1020408 caret turds when changing modes from non-scrolling to scrolling in cmdtool 1097384 Popup menus don't work when frame in xv_window_loop mode 1076907 destroying command frame leaks memory 1043723 underline does not work in shelltool 1101846 WIN_BORDER causes window to be created whose width or height can be -1 1066919 cmdtool/tip exits when ctl-C sent to tip 1103579 A combination of help / F1 and owplaces can crash the shelltool 1105512 menus hang after ACTION_ADJUST 1106032 Pinned find causes segv when parent destroyed 1098466 Patch 100452-12 or earlier causes menus to display horizontally 1106525 Xview3.0 keypad doesn't behave as documented 1093908 Exclusive scrolling-list does not work fine if it is sorted with PANEL_LIST_SORT 1067716 mailtool & filemgr dumps core in selection code (losing ownership) 1109382 notices cannot be confirmed with RETURN 1108767 Arrow keys no longer traverse panels 1112589 PgUp and PgDn doesn't work on type-5 center keypad 1113021 textsw on dual headed display dies with BadMatch 1110227 xview patch 100452-20 breaks debug malloc 1109875 SHIFT key does not reverse NUM_LOCK on right keypad 1114662 Up and Down cursor keys don't work in textsw 1111308 Application doesn't run after installing patch 100452-02 1114561 xv_destroy on a server object dumps core 1065350 notifier occasionally fails to deliver itimer events 1067367 Numeric text fields in panel have a bad value when left blank 1115954 xview patch 100452-25 alters the behavior of program, if "-Wx large" option used 1053622 PANEL_CLIENT_DATA wrong in PANEL_NUMERIC_TEXT event proc 1109875 SHIFT key does not reverse NUMLOCK 1122244 textedit -read_only goes into infinite loop 1122239 textedit core dumps when dropping a compressed file 1122353 textedit will hang when selecting and copying more than one page of text. 1072252 textedit core dump because of simple operation in a split window! 1117789 Patch 100452-28 causes reoccurance of bug: 1106032 1071584 Panel scrolling list doesn't scroll when using xv_window_loop() function call. 1124324 dbx warning message after loading patch id 100452-35 (xview CTE patch) 1066669 Vi and Cmdtool do not redraw wide window correctly. 1098379 BadValue when creating multiline text field on wierd size control area 1131411 setting PANEL_LIST_WIDTH is very slow when dealing with long list items 1129722 SERVER_EXTERNAL_XEVENT_PROC only works for root window 1140264 AGAIN key with 100452-25 to -44 broke supports for multiple-action usages 1134887 PANEL_VALUE_STORED_LENGTH not compatible with OW-2.0 1140806 textsw and ttysw leak memory 1136974 paste/find gets confused and uses stale value 1139167 rev 15 to 47 of XView 3.0 patch 100452 can overwrite memory on rare occasions 1142387 rev 38 of XView 3.0 patch 100452 does not allow for programmatic insertions into a textsw which makes the SunNet Manager browser unable to display log data on OW3_U1. 1047558 App dumps if mouseless is on, and current object is destroyed 1140250 xv_destroy() on top level menu with pullright submenus can cause SEGV 1148561 Scrolling in cmdtool jumps with very long lines 1148724 Destroying an active menu in stay-up mode causes core dump. 1110936 Single character text fields do not work when wide characters are inserted 1149528 XView patch 100452-51 breaks SunNet Manager. 1148277 Backspace/Delete leaves half care image behind. 1145729 Copy/Paste frequently fails in OpenWindows 3.3. 1161640 MENU_VALUE is set to other than an XView object can cause core dump 1160672 shelltool doesn't report correct screen size 1161637 Destroying read only PANEL_TEST items can dump core 1161924 editing near the end of a textinput item that is scrolling is broken 1164206 Customer's code hangs and core dumps in xview 1164512 Menus don't pop down 1137807 termsw's & ttysw's spew ttysw_sigwinch warning messages in BCP mode 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: //installpatch / where is the directory containing the patch and is the patch number. must be a full path name. Example: # /tmp/123456-01/installpatch /tmp/123456-01 3. If any errors are reported, see "Patch Installation Errors" in the Command Descriptions section below. Rebooting the system or restarting the application after a successful patch installation is usually necessary to utilize patch. NOTE: 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 the next section for instructions for installing a patch on a client. Instructions for installing a patch on a diskless or dataless client -------------------------------------------------------------------- 1. Before applying the patch, the following command must be executed on the server to give the client read-only, root access to the exported /usr file system so that the client can execute the pkgadd command: share -F nfs -o ro,anon=0 /export/exec//usr The command: share -F nfs -o ro,root= \ /export/exec//usr accomplishes the same goal, but only gives root access to the client specified in the command. 2. Login to the client system and become super-user. 3. Continue with step 2 in the "Instructions to install patch using installpatch" section above. Instructions for backing out patch using "backoutpatch" ------------------------------------------------------- 1. Become super-user. 2. Change directory to /var/sadm/patch: cd /var/sadm/patch 3. Backout patch by typing: /backoutpatch where is the patch number. Example: # 123456-01/backoutpatch 123456-01 4. If any errors are reported, see "Patch Backout Errors" in the Command Descriptions section below. Instructions for identifying patches installed on system: ---------------------------------------------------------- Patch packets that have been installed can be identified by using the showrev command with the "-p" option: showrev -p Also note that installpatch has a similar "-p" option which will also just identify patches already installed. Command Descriptions -------------------- NAME installpatch - apply patch package to Solaris 2.x system backoutpatch - remove patch package, restore previously saved files SYNOPSIS installpatch [-udpV] [-S ] backoutpatch [-fV] [-S ] DESCRIPTION These installation and backout utilities apply only to Solaris 2.x associated patches. They do not apply to Solaris 1.x associated patches. These utilities are currently only provided with each patch package and are not included with the standard Solaris 2.x release software. OPTIONS installpatch: -u unconditional install, turns off file validation. Allows the patch to be applied even if some of the files to be patched have been modified since original installation. -d Don't back up the files to be patched. This means that the patch can't be backed out. -p Print a list of the patches currently applied -V Print script version number -S Specify an alternate service (e.g. Solaris_2.3) for patch package processing references. backoutpatch: -f force the backout regardless of whether the patch was superseded -V print version number only -S Specify an alternate service (e.g. Solaris_2.3) for patch package processing references. DIAGNOSTICS Patch Installation Errors: -------------------------- Error message: Patch has already been applied. Explanation and recommended action: This patch has already been applied to the system. If the patch has to be reapplied for some reason, backout the patch and then reapply it. Error message: This patch is obsoleted by patch which has already been applied to this system. Patch installation is aborted. Explanation and recommended action: Occasionally, a patch is replaced by a new patch which incorporates the bug fixes in the old patch and supplies additional fixes also. At this time, the earlier patch is no longer made available to users. The second patch is said to "obsolete" the first patch. However, it is possible that some users may still have the earlier patch and try to apply it to a system on which the later patch is already applied. If the obsoleted patch were allowed to be applied, the additional fixes supplied by the later patch would no longer be available, and the system would be left in an inconsistent state. This error message indicates that the user attempted to install an obsoleted patch. There is no need to apply this patch because the later patch has already supplied the fix. Error Message: None of the packages to patch are installed on this system. Explanation and recommended action: The original packages for this patch have not been installed and therefore the patch cannot be applied. The original packages need to be installed before applying the patch. Error message: This patch is not applicable to client systems. Explanation and recommended action: The patch is only applicable to servers and standalone machines. Attempting to apply this patch to a client system will have no effect on the system. Error message: The /usr/sbin/pkgadd command is not executable. Explanation and recommended action: The /usr/sbin/pkgadd command cannot be executed. The most likely cause of this is that installpatch is being run on a diskless or dataless client and the /usr file system was not exported with root access to the client. See the section above on "Instructions for installing a patch on a diskless or dataless client". Error message: packages are not proper patch packages. Explanation and recommended action: The patch directory supplied as an argument to installpatch did not contain the expected package format. Verify that the argument supplied to installpatch is correct. Error message: The following validation error was found: Explanation and recommended action: Before applying the patch, the patch application script verifies that the current versions of the files to be patched have the expected fcs checksums and attributes. If a file to be patched has been modified by the user, the user is notified of this fact. The user then has the opportunity to save the file and make a similar change to the patched version. For example, if the user has modified /etc/inet/inetd.conf and /etc/inet/inetd.conf is to be replaced by the patch, the user can save the locally modified /etc/inet/inetd.conf file and make the same modification to the new file after the patch is applied. After the user has noted all validation errors and taken the appropriate action for each one, the user should re-run installpatch using the "-u" (for "unconditional") option. This time, the patch installation will ignore validation errors and install the patch anyway. Error message: Insufficient space in /var/sadm/patch to save old files. Explanation and recommended action: There is insufficient space in the /var/sadm/patch directory to save old files. The user has two options for handling this problem: (1) generate additional disk space by deleting unneeded files, or (2) override the saving of the old files by using the "-d" (do not save) option when running installpatch. However if the user elects not to save the old versions of the files to be patched, backoutpatch CANNOT be used. One way to regain space on a system is to remove the save area for previously applied patches. Once the user has decided that it is unlikely that a patch will be backed out, the user can remove the files that were saved by installpatch. The following commands should be executed to remove the saved files for patch xxxxxx-yy: cd /var/sadm/patch/xxxxxx-yy rm -r save/* rm .oldfilessaved After these commands have been executed, patch xxxxxx-yy can no longer be backed out. Error message: Save of old files failed. Explanation and recommended action: Before applying the patch, the patch installation script uses cpio to save the old versions of the files to be patched. This error message means that the cpio failed. The output of the cpio would have been preceded this message. The user should take the appropriate action to correct the cpio failure. A common reason for failure will be insufficient disk space to save the old versions of the files. The user has two options for handling insufficient disk space: (1) generate additional disk space by deleting unneeded files, or (2) override the saving of the old files by using the "-d" option when running installpatch. However if the user elects not to save the old versions of the files to be patched, the patch CANNOT be backed out. Error message: Pkgadd of package failed with error code . 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