Motif ALPMOTF08_U3012 DECwindows Motif V1.2-3 Alpha ECO Summary

TITLE: Motif ALPMOTF08_U3012 DECwindows Motif V1.2-3 Alpha ECO Summary Modification Date: 06-JAN-99 Modification Type: DOCUMENTATION: Editorial Modification Moved Kit from Motif Directory to DECwindows_Motif Directory on the FTP Site NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. The name of the compressed file will be kit_name-dcx_vaxexe for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha. Once the file is copied to your system, it can be expanded by typing RUN compressed_file. The resultant file will be the OpenVMS saveset or PCSI installation file which can be used to install the ECO. Copyright (c) Digital Equipment Corporation 1995, 1998. All rights reserved. PRODUCT: DECwindows Motif[R] for OpenVMS Alpha, Version 1.2-3 COMPONENTS: Bitmap File Bookreader C++ Compilation CDA Library CDA Viewer DECimage Application Services (DAS) DEClinks (LinkWorks) DECterm DECwindows Mail DXm Library 1.1.3 DXm Library 1.2.3 Dwt (XUI) Library Internationalization Kit Installation Login Motif Window Manager (mwm) 1.2.3 Notepad Session Manager / FileView Startup UIL Compiler 1.2.3 Xlib Xm Library 1.1.3 Xm Library 1.2.3 Xt Intrinsics Library R4 OP/SYS: OpenVMS Alpha SOURCE: Digital Equipment Corporation ECO INFORMATION: ECO Kit Name: ALPMOTF08_U3012 ECO Kits Superseded by This ECO Kit: ALPMOTF07_U3012 AXPMOTF06_U3012 AXPMOTF05_U3012 (AXPMOTF) ECO Kit Approximate Size: 41162 Blocks Saveset A: 41013 Blocks Kit Applies To: DECwindows Motif V1.2-3 System Reboot Necessary: No Installation Rating: 3 - To be installed on all systems running the listed versions of OpenVMS which are experiencing the problems described. ECO KIT SUMMARY: An ECO kit exists for DECwindows Motif V1.2-3. This kit addresses the following problems: PROBLEMS ADDRESSED IN ALPMOTF08_U3012 KIT: Session Manager problems o In customizing the colors in the session manager, if the color model menu is torn off, the session manager will crash when a model is selected. This problem is corrected in the remedial kit. FileView problems o Using the Print dialog invoked from FileView to print a file prints the wrong set of pages if the "From" field is completed. This problem is corrected in the remedial kit. Print Screen problems o When DECW$PRINTSCREEN generates a PostScript file it writes introductory comments to this file. After the end of 1999 the date written to the file will be wrong. For example, the year 2000 would be output as "19100". This problem is corrected in the remedial kit. Paint problems o When DECW$PAINT generates a PostScript file it writes introductory comments to this file. After the end of 1999 the date written to the file will be wrong. For example, the year 2000 would be output as "19100". This problem is corrected in the remedial kit. DECwindows Mail problems o When invoking the Extract dialog from a mail message DECwindows Mail can terminate with an access violation. This problem is corrected in the remedial kit. o Sometimes spurious horizontal lines will be left in the main display for mail. This problem is corrected in the remedial kit. o The AXPMOTF07_U3012 kit introduced a problem where DECwindows Mail can terminate abnormally. This happens if the tree display is in use and a message is dragged to a folder which was not visible when the drag started. This problem is corrected in the remedial kit. CDA Viewer problems o When converting DTIF files to DDIF and the current year is 2000 or later, the year is written incorrectly to the DDIF file: the first two digits of the year are always written as 19. This problem is corrected in the remedial kit. Notepad problems o When text including the last character in the display is selected and deleted the display sometimes fails to be updated. This problem is corrected in the remedial kit. Display Postscript problems o In DECwindows Motif V1.2-3, when viewing PostScript files with the CDA Viewer application and displaying to an Alpha workstation, 8 bit ASCII characters do not appear. This problem is corrected in the remedial kit. Xlib problems o In DECwindows Motif V1.2-3, if a program enters its event loop (e.g. by calling XtAppMainLoop) without having opened a display or specified a timer or event flag for the program to wait for (by calling XtAppAddTimeout or XtAppAddInput), Xlib will terminate the program with the following error message: X Toolkit Error: Error in XMultiplexInput This problem is corrected in the remedial kit. In the situation where there is nothing to wait for, Xlib will wait forever instead of terminating with an error status. To allow Xlib to process events at a later time applications should provide some means of regaining control, such as by specifying an event flag in a call to XtAppAddInput. DXM Library problems o Creating a gray-scale colormix widget causes an ACCVIO. This problem is corrected in the remedial kit. o Using the help widget, the visit topic option always displays a window with left to right text display. The text direction should be inherited from the help widget. This problem is corrected in the remedial kit. o With the DXmCSText widget, replacement of text can fail and sound the bell instead. The problem occurs if the text field is at the maximum length and some of it has been selected for replacement. This problem is corrected in the remedial kit. o If parts of the print widget are suppressed, the display can be poorly formatted and unusable. This problem is corrected in the remedial kit. o Using the CtrlosfDown and CtrlosfUp keys to move up or down an Svn widget display does not leave the location correctly defined. This can cause various errors when an operation is subsequently executed. This problem is corrected in the remedial kit. XM Library problems o With a vertical scale widget, the position of the slider can be miscalculated and displayed below the end of the scale. The problem occurs only when the label is long or uses a large font. This problem is corrected in the remedial kit. o Various problems can be observed when using drag and drop between windows on different screens of a multi-headed configuration. These problems may occur when the root window or color maps are configured differently on the two screens. These problems are corrected in the remedial kit. o Use of pixmaps can result in memory leaks within a client application. This problem is corrected in the remedial kit. o If the orientation of a scrollbar widget is changed, its thickness is not recalculated. Since the thickness can depend upon the orientation, the scrollbar will be incorrectly displayed. This problem is corrected in the remedial kit. o When a text widget is destroyed there is a small, unavoidable, memory leak in the client application. This problem is corrected in the remedial kit. o XmStringGetCurrentCharSet uses a default locale found by translating the logical name "XNL$LANG". Everywhere else in DECwindows Motif 1.2-3 the default locale is found by translating the logical name "LANG". The remedial kit uses "LANG" for the default locale. o If a scrolled window is created and the text direction for the window is changed, then the vertical scrollbar should be moved to the other side of the window. This was not happening. This problem is corrected in the remedial kit. PROBLEMS ADDRESSED IN ALPMOTF07_U3012 KIT: NOTE: These problems are corrected in DECwindows Motif V1.2-4. Kit Installation Problems: o The AXPMOTF05_U3012 kit installation procedure always installs the following Example and Programming files even if those options were not selected during the installation of DECwindows Motif V1.2-3. SYS$SYSTEM:DECW$UILMOTIF.EXE SYS$SYSTEM:DECW$WML.EXE DECW$INCLUDE:XMOSP.H DECW$SYSTEM_DEFAULTS:DECW$UIL_OSF_MOTIF_1_1.WML DECW$SYSTEM_DEFAULTS:DECW$UIL_OSF_MOTIF_1_1.WMD DECW$SYSTEM_DEFAULTS:DECW$UIL_DXM_MOTIF.WML DECW$SYSTEM_DEFAULTS:DECW$UIL_DXM_MOTIF.WMD SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]HLINES2.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]LEFT_PTR.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]LEFT_PTRMSK.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]LIGHT_GRAY.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]MENU8.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]OPENDOT.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]OPENDOTMASK.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]RIGHT_PTR.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]RIGHT_PTRMSK.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]ROOT_WEAVE.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]SCALES.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]STAR.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]STARMASK.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]STIPPLE.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]TARGET.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]TIE_FIGHTER.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]VLINES2.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]WEIRD_SIZE.XBM SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]WIDE_WEAVE.XBM This problem is corrected in the ALPMOTF07_U3012 remedial kit. However, optional files that were installed by the AXPMOTF05_U3012 remedial kit are not deleted. Startup Problems: o In the AXPMOTF05_U3012 remedial kit console broadcasts are not disabled or enabled if OPA0: is owned by another process during DECwindows startup, regardless of the setting of DECW$CONSOLE_SELECTION. This problem did not exist in DECwindows Motif V1.2-3. o In DECwindows Motif V1.2-3, console broadcasts are enabled if the system was booted from an alternate console, even if DECW$CONSOLE_SELECTION is set to its default value of "ENABLE". o In DECwindows Motif V1.2-3, the following error message is displayed during DECwindows startup if the system was booted from an alternate console: %SDA-E-NOTINPHYS, 0000000000000024 : virtual data not in physical memory o In DECwindows Motif V1.2-3, the startup customizations in DECW$PRIVATE_APPS_SETUP.COM are ignored if the logical name DECW$IGNORE_WORKSTATION is defined. DECW$IGNORE_WORKSTATION is a system logical name that tells the DECwindows startup procedure not to start the X11 display server, but it does not prevent the system from being used as an X11 client. Login Problems: o In the AXPMOTF05_U3012 remedial kit, when the DECwindows Login program displays an error message, such as when the user enters an invalid password, the error message dialog box briefly flashes at the upper left corner (0,0) before being centered on the screen. This problem did not occur in DECwindows Motif V1.2-3. Session Manager / FileView Problems: o In DECwindows Motif V1.2-3, resource information read from a VUE$PROFILE.VUE$DAT file located in VUE$LIBRARY will take precedence over information stored in the DECW$USER_DEFAULTS:VUE$PROFILE.VUE$DAT file. o In DECwindows Motif V1.2-3, if the user types "MCR VUE$MASTER -ICONIC", Fileview will not start as an icon (it ignores the -ICONIC). o In DECwindows Motif V1.2-3, there is a problem with the Fileview Type command where the output window may not come up the first time. To make the window appear, the user must go into the Work In Progress dialog box and select Show Output. o In DECwindows Motif V1.2-3, modifying a Menu from the Options Menu... pulldown in Session Manager or Fileview toggles the default run type qualifiers for all applications. If the applications are defined to run as subprocesses they will be changed to run as detached processes when the OK button is selected. o In the AXPMOTF05_U3012 remedial kit, when an application uses the XmScrolledWindow widget and scroll bars are added automatically they appear in the dialog box instead of in the scrolled window. The bottom of the scrolled window does not move together with the bottom of the form that it is attached to. This problem was caused by the following resource definition in DECW$SYSTEM_DEFAULTS: DECW$SMB_WINDOW.DAT: *DXmfitToScreenPolicy: AS_NEEDED This resource is not defined in DECwindows Motif V1.2-3, and there is no problem with XmScrolledWindow widgets. o In DECwindows Motif V1.2-3, the Session Manager can terminate with an ACCVIO after a server error when output is directed to an X server that does not support Digital's XSME server extension, such as a PC X server. o In DECwindows Motif V1.2-3, under some circumstances the Session Manager can terminate with an ACCVIO when the user logs in, due to a problem with it setting icon pixmaps for its dialog boxes. DECterm Problems: o In DECwindows Motif V1.2-3, if DECterm is set to Printer Controller mode pointing to a print queue (or if printing to the same file or port), the DECterm controller will crash if two DECterms try to print at once. o In DECwindows Motif V1.2-3 DECterm ignores the first parameter of the ReGIS escape sequence, which tells ReGIS to start a new context or resume where it left off, and always resumes where it left off. This can cause problems when frequently exiting and entering ReGIS, especially if the last ReGIS command was a Text command and ReGIS was exited in the middle of the command. This causes DECterm to interpret the new ReGIS commands as text, and to display the commands on the screen instead of actually executing them. This problem occurs on all versions of DECwindows Motif on Alpha systems. Bookreader Problems: o In DECwindows Motif V1.2-3, Bookreader print removes characters, leaves incomplete lines and has problem formatting paragraphs, topics and chapters. Bookreader also prints multiple instances of graphics. Because of the number of problems with print and the quality of the output the print function has been rewritten. DECwindows Mail Problems: o In DECwindows Motif V1.2-3, when working in the Create window, using the Search and Replace menu item to do a Replace All will cause Mail to ACCVIO when the OK button is hit. o In DECwindows Motif V1.2-3, if the user has a Read window and a Search window for the Read window up and then presses Move in the Read window, DECwindows Mail will ACCVIO. o In DECwindows Motif V1.2-3, DECwindows Mail will ACCVIO when the user uses MB2 to paste into a Reply (Create) window if the folder selection window style is set to paned. CDA Viewer Problems: o In DECwindows Motif V1.2-3, when CDA Viewer is run as a detached process it doesn't exit when the user ends the session. Instead it goes into a loop writing the following error message to SYS$OUTPUT: Error in XMultiplexInput Notepad Problems: o In DECwindows Motif V1.2-3, Notepad always updates the revision date of a file, even if it was not edited, e.g. if the user immediately used the Quit or Exit command. Xm Library 1.2.3 Problems: o In previous versions of DECwindows Motif, a user could activate an option menu using either the mouse or the keyboard "space" bar and then to select one of the options by using either the mouse or the keyboard. In DECwindows Motif V1.2-3, if the option menu is activated with the keyboard, the user cannot select an option using the mouse. o In DECwindows Motif V1.2-3, applications can crash when managing and unmanaging nested dialog shells. o In DECwindows Motif V1.2-3, a Motif application will terminate with an access violation if its _MOTIF_DRAG_WINDOW is deleted. In the reported case, the login box failed to come up because a server problem caused this window to be deleted. o In DECwindows Motif V1.2-3, under various conditions, it is possible to get incorrect behavior during Drag and Drop operations on multi-headed workstations. This behavior includes incorrect cursor being displayed, popup indicators shown on the wrong screen, locking the X server, and corrupted drag cursors. It is also possible to get the following error messages: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 72 (X_PutImage) X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 62 (X_CopyArea) o In DECwindows Motif V1.2-3, there is a memory leak when hashing into an occupied space. o In DECwindows Motif V1.2-3, the File Selection Box (FileSB) widget does not return the correct filename when pathMode is set to XmPATH_MODE_RELATIVE and the user enters a directory name without pressing the Apply button. o In DECwindows Motif V1.2-3, a Scrolled List widget's width is not properly adjusted when it is unmanaged using XtSetArg and XtSetValues, and then managing it again. If two Scrolled Lists are created and unmanaged, then resized by calling XtSetArg and one of them is managed again, the changed size is not reflected. o In DECwindows Motif V1.2-3, when the XmNforeground resource of either the XmText or XmTextField widget is toggled rapidly between two colors, a memory leak occurs. o In DECwindows Motif V1.2-3, under certain circumstances, two buttons in a Radio Box widget or gadget can be displayed in a depressed state at the same time. o In DECwindows Motif V1.2-3, there are two leaks in the List widget. In the first, using CopyItems() twice leaks memory because, on the second call, data is really being copied internally. In the second, the List widget's destroy method failed to remove the XmNDestroyCallback list. o In DECwindows Motif V1.2-3, it is not possible to use the return key to open an entry in the SVN widget, such as in Bookreader and in DECwindows Mail. This is inconsistent with previous versions of Motif. o In DECwindows Motif V1.2-3, DXmActivateWidget fails on pushbuttons in a menu. The application displays the following error message: X Toolkit Error: Couldn't find per display information and terminates. o In DECwindows Motif V1.2-3, a busy X server can appear to be hung when a user has attempted to post the Motif Window Manager (mwm) menu by double-clicking on the root window while alternately selecting a menu item from the Session Manager menu. The pointer tracks, but selections are not activated. Stopping and re-starting the window manager 'frees' the X server. o In DECwindows Motif V1.2-3, there is a memory leak in the cvtXmStringToText() function in the Xm library. o In DECwindows Motif V1.2-3, the X server leaks memory due to the Xm library not freeing pixmaps and because of caching problems in the Xm library. o In DECwindows Motif V1.2-3, there was a dramatic performance degradation when managing complex widget hierarchies, compared with previous versions of Motif. o In DECwindows Motif V1.2-3, pressing TAB in a window with only one tab group does not set focus to the "home" widget. o In DECwindows Motif V1.2-3, if an application calls RemoveGrab() to remove a widget while another widget is being destroyed, RemoveGrab() does not re-add the widget being destroyed onto the grab list so that it can later be removed from the grab list correctly. o In DECwindows Motif V1.2-3, some created windows are insensitive to user input. o In DECwindows Motif V1.2-3, there is a memory leak in XtSetValues() for Text widgets. o In DECwindows Motif V1.2-3, on-the-spot input does not operate correctly. o In DECwindows Motif V1.2-3, there is a problem with the Text widget, in that its handling of shifting lines up or down causes memory corruption. o In DECwindows Motif V1.2-3, the XmTextField widget leaks memory when the widget is destroyed. o In DECwindows Motif V1.2-3, an access violation occurs when an application program calls XtVaSetVValues() to set the XmNvalue resource while text is selected in an XmTextField widget. DXm Library 1.2.3 Problems: o In DECwindows Motif V1.2-3, when the help widget is displaying two topics of the same length, the first topic comes up in a few seconds. The second topic, however, can take up to two minutes to appear. o In DECwindows Motif V1.2-3, the SVN widget leaves behind parts of the highlight frame when it scrolls down past the bottom entry in a window. o In DECwindows Motif V1.2-3, when directing the SVN widget to other than the default screen (that is, if the display is set to screen 0 with the SET DISPLAY command and the application program's command line directs it to display to screen 0), then the program can fail with the following error: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 55 (X_CreateGC) UIL Compiler 1.2.3 Problems: o In DECwindows Motif V1.2-3, when a UIL file is compiled that sets the XmNdefaultButtonType to XmDIALOG_NONE the following error occurs: $ UIL/MOTIF test.uil XmNdefaultButtonType = XmDIALOG_NONE; * %UIL-E-NEVER_DEF, value XmDIALOG_NONE was never defined o In DECwindows Motif V1.2-3, when compiling a UIL file containing references to a custom widget defined in a WMD file, %UIL-E-CREATE_PROC_REQ and %UIL-W-UNSUPPORTED errors are reported when an XmWorkingDialog widget is defined in the UIL file. o In DECwindows Motif V1.2-3, when a UIL file tries to include a file that is in the default directory, it prints the following error: %UIL-F-SRC_OPEN, error opening source file: xxx.uil o In DECwindows Motif V1.2-3, when running the WML compiler to create a custom WMD file, the following error message may be displayed: %UIL-F-BAD_DATABASE, error reading binary database o In DECwindows Motif V1.2-3, DECW$WML.EXE always reads DECW$WML_TOKENS.DAT from SYS$LIBRARY. In the remedial kit DECW$WML.EXE will first look for DECW$WML_TOKENS.DAT in the current directory before looking in SYS$LIBRARY. This allows the use of a customized tokens file. o In DECwindows Motif V1.2-3, the f.next_key function, which cycles through windows on the screen, does not cycle properly through windows whose Input Hint is False. The Window Manager should skip windows that have their Input Hint set to False. Xm Library 1.1.3 Problems: o In DECwindows Motif V1.2-3, when doing a cut and paste operation using the clipboard, the process can terminate with an access violation. Xt Intrinsics Library R4 Problems: o In DECwindows Motif V1.2-3, at apparently random times, an application program can terminate with an access violation, due to a problem with keyboard handling. o In DECwindows Motif V1.2-3, there is sometimes a five second delay in creating dialog boxes because the shell widget's geometry manager is waiting for an event that is not received. o colorConvertArgs and screenConvertArg have been added as universal symbols in DECW$XTLIBSHRR5.EXE in the remedial kit. These data structures are described in Section 9.6.4 of the book X Window System Toolkit by Asente and Swick. However, the declarations of these routines in Intrinsic.h has not been enabled for OpenVMS. A program that references these data structures will not run correctly on DECwindows Motif V1.2-3, unless the remedial kit is installed, because the addresses of the data structures within DECW$XTLIBSHRR5.EXE have changed. For this reason, programs wishing to use colorConvertArgs or screenConvertArg should either declare local copies of these data structures, which are very small and have well defined contents, or else find their addresses by calling LIB$FIND_IMAGE_SYMBOL. o _XtperDisplayList has been added as a universal symbol in DECW$XTLIBSHRR5.EXE in the remedial kit. The symbol is available for use by third party products but is unsupported and the contents of this data structure may change in future versions of DECwindows Motif. Because the location of this data structure within DECW$XTLIBSHRR5.EXE was different in previous versions of DECwindows Motif, it should be accessed by calling LIB$FIND_IMAGE_SYMBOL. Dwt (XUI) Library Problems: o In DECwindows Motif V1.2-3, when doing a cut and paste operation in DECchart using the clipboard, the session hangs. The process terminates and produces a dump file, but the window continues to show the hourglass, waiting for a response. When pasting text into a message using the clipboard in DEC MailWorks, the client application terminates, taking the user to the DCL prompt. An access violation and stack dump are generated. o In DECwindows Motif V1.2-3, when an item is deleted from a List Box with DWT.LIST_BOX_DELETE_POS or DWT.LIST_BOX_DELETE_ITEM, the horizontal scrollbar may be reset to the maximum so that the user is no longer able to view the entire item. The problem appears when the number of items is less than the maximum number of visible items. Xlib Problems: o In DECwindows Motif V1.2-3, X$GET_WINDOW_PROPERTY does not load the correct number of bytes into the calling routine's data buffer. o In DECwindows Motif V1.2-3, user defined timeouts are disabled if XFlush is called after the user has disabled AST recognition. o In DECwindows Motif V1.2-3, XReconfigureWMWindow does not trap BadMatch errors. o In DECwindows Motif V1.2-3, if too many displays are opened XOpenDisplay signals a %XLIB-W-MAXOPENDSP error but returns a non-zero value. CDA Library Problems: o In DECwindows Motif V1.2-3, programs can terminate with an ACCVIO when converting graphics files to DDIF format by calling CDA$STORE_ITEM. C++ Compilation Problems: o In DECwindows Motif V1.2-3, users of C++ will receive an undefined symbol on XUNIQUECONTEXT__XV when linking with a module that references XUniqueContext. o The Display PostScript header files provided with DECwindows Motif V1.2-3 are not C++ compliant. Software developed with DEC C++ generates compilation and link errors when linked with the following header files in XDPS$INCLUDE: DPSCLIENT.H DPSCUSTOMOPS.H DPSEXCEPT.H DPSFRIENDS.H DPSOPS.H DPSXCLIENT.H PSCUSTOMOPS.H PSOPS.H XDPS.H XDPSLIB.H Internationalization Problems: o In DECwindows Motif V1.2-3, the DECwindows Login and Pause programs terminate with an ACCVIO on OpenVMS Alpha V6.2 systems using the Hebrew keyboard. o In DECwindows Motif V1.2-3, after changing to a preferred language, e.g. German or French, executing the following multiplication in Calculator, 2,5 * 2,5, would get 4 as the result. It should be 6.25. o Two internationalization fixes were merged into mwm for the remedial kit. The first has to do with activation of the customize and help functions by a buttonEvent. The second was made to prevent Hebrew titles from appearing in reverse order. o In DECwindows Motif V1.2-3, a program running in the Hangul locale with terminate with an ACCVIO if the user presses the shift and compose keys. o In DECwindows Motif V1.2-3, programs running in the Hangul locale terminate with an ACCVIO because of a problem with calls to the _DXmCSTextScanWord routine. o In DECwindows Motif V1.2-3, programs running in the Thai locale terminate with an ACCVIO because the following routines are missing from DECW$DXMLIBSHR12.EXE: _DWMotifV12Compat _DXmCSTextGetSelection _DXmCSTextScanCompositeBreak _DXmCSTextSourceInsertString _DXmCSTextSrcPreeditReplaceStr o In DECwindows Motif V1.2-3, when tearing off menus, the title of the newly created Dialog Box contains the name of option, followed by "Tear-off", written in English. For localized applications, this produces a mixture of native and English text in the Dialog Box title. For example, after tearing off the View menu from the French Calendar, the following Dialog Box title is displayed: "Visualisation Tear-off" o In DECwindows Motif V1.2-3, the performance of the string parsing in the XmTextInsert function is very poor for the Japanese and Asian locales. Error Reporting Improvements: o In DECwindows Motif V1.2-3, the error traceback output that DECwindows Mail and FileView write to SYS$OUTPUT after an exception includes the version number V1.2-941206, which is misleading because it implies that the DECwindows Motif version number is V1.2. These programs will now write a version number of V1.2-3960215. o In DECwindows Motif V1.2-3, the DECW$LOGIN.LOG file does not include the DECwindows version number, the date and time that the log file was created, the error status returned from an XOpenDisplay failure, or a message stating that the display was successfully opened. This additional information is written to DECW$LOGIN.LOG in the remedial kit. The DECW$LOGIN.LOG file can be created by adding the following global symbol definition to SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM and then restarting DECwindows: $ DECW$LOGINLOG == "SYS$MANAGER:DECW$LOGIN.LOG" o In DECwindows Motif V1.2-3, misleading error messages can be written to DECW$LOGIN.LOG after an exception. For example, after the user enters a bad password the following error messages are written to SYS$OUTPUT: User authorization failure error detected: non-translatable VMS error code: 0x186D4, VMS message: %RMS-F-SYN, file specification syntax error The "file specification syntax error" message has nothing to do with the actual problem, which is a user authorization failure. Problems Addressed in the AXPMOTF06_U3012 Kit: o When running DECwindows Motif V1.2-3 on an OpenVMS Alpha V7.0 system and using the DECwindows interface to Notes, Notes fails to open remote notes conferences, displaying the following error message: LinkWorks Reported Error: Unknown error This problem is triggered by DECthreads support for multithreads. DECwindows Notes makes calls into the DEClinks (previously known as LinkWorks) library LWK$DXMSHR.EXE, which is no longer supported as of DECwindows Motif V1.2-3. This problem is corrected in DECwindows Motif V1.2-4. Problems Addressed in the AXPMOTF05_U3012 Kit: NOTE: These problems are corrected in DECwindows Motif V1.2-4. Startup Problems: o Whenever DECwindows V1.2-3 is started, it purges SYS$LIBRARY:DECW$*.EXE and SYS$SYSTEM:DECW$SETSHODIS.EXE. This could lead to files being lost when DECwindows is started after installing a new version of DECwindows Motif in a clustered environment when another node still has an earlier version of the files open. In this scenario it is possible for these files to be lost and the disk space not freed. To resolve this, the entire cluster must be rebooted then an ANALYZE/DISK/REPAIR must be done on the disk containing the lost files. o In DECwindows Motif V1.2-3, if WINDOW_SYSTEM is not set to 1, DECwindows will not start without a reboot. This is true even if the system does not have a graphics device. The DECwindows startup procedure has been modified so that it sets WINDOW_SYSTEM to 1 if it was previously 0 on workstations only, and doesn't change the value of WINDOW_SYSTEM on non-workstations. DECwindows startup now continues regardless of the value of WINDOW_SYSTEM. To prevent the DECwindows X11 display server from starting on a workstation, either define the logical name DECW$IGNORE_WORKSTATION with a value of TRUE or set WINDOW_SYSTEM to 2. Note that setting WINDOW_SYSTEM to 2 will start VWS (UIS) on a system that has the VAX Workstation Software product installed. If VWS is installed on your system and you don't want any windowing system to start, you should boot your system with WINDOW_SYSTEM set to either 0 or 1 and with STARTUP_P1 set to "MIN". You can then edit your SYS$STARTUP:SYSTARTUP_VMS.COM file and define the logical name DECW$IGNORE_WORKSTATION with a value of TRUE. o In DECwindows Motif V1.2-3, the command procedure DECW$STARTAPPS.COM disables broadcasts to the console terminal during system startup whether or not the system has a graphics adapter or a alternate console. This kit fixes this problem by only disabling console broadcasts on systems that have a graphics adapter and are not using an alternate console. o In DECwindows Motif V1.2-3, DECW$STARTAPPS.COM does not install the SYS$LIBRARY:DECW$MAILSHR12.EXE shareable library as a known image. o When running under OpenVMS Alpha V6.2, DECwindows Motif V1.2-3 does not allow the user to restart DECwindows unless the logical name DECW$IGNORE_SHARED_ADDRESS is defined with a value of "TRUE". This has been changed so that DECwindows can be restarted; however, the startup procedure will not install/replace the shareable images in this situation. o In DECwindows Motif V1.2-3, there is a requirement that the SYSGEN parameter GH_RSRVPGCNT be set to a minimum of 512 on OpenVMS Alpha V6.2 systems, in order to allow DECwindows images to be installed with shared linkage sections. This unnecessarily consumes system resources since not all of the reserved pages are actually used. OpenVMS Alpha V6.2 will temporarily increase GH_RSRVPGCNT during system startup to allow DECwindows to install images with shared linkage sections, and it will lower GH_RSRVPGCNT after startup is complete. Therefore, in the remedial kit the DECwindows Motif startup procedure no longer imposes a minimum value for GH_RSRVPGCNT. This frees up physical memory for other uses. When DECwindows Motif V1.2-3 is installed on an OpenVMS Alpha V6.2 system it will invoke AUTOGEN to set a minimum value for GH_RSRVPGCNT in the file SYS$SYSTEM:CLU$PARAMS.DAT. To avoid excessive use of physical memory, after installing this remedial kit on an OpenVMS Alpha V6.2 system you should edit SYS$SYSTEM:CLU$PARAMS.DAT and remove all references to GH_RSRVPGCNT, and then invoke SYS$UPDATE:AUTOGEN.COM to reset the parameter to its default value. However, if DECwindows is not started during system startup, or if it is started initially without using shared linkage sections, you won't be able to start DECwindows with shared linkage sections (which is the default) later unless you either increase GH_RSRVPGCNT to 512 or else reboot the system. Therefore, on an OpenVMS Alpha V6.2 system, if you disable the initial startup of DECwindows but plan to start DECwindows some time after system startup has completed, either set the minimum value of GH_RSRVPGCNT to at least 512 on your system or add the following logical name definition to your SYS$STARTUP:SYSTARTUP_VMS.COM file: $ DEFINE/SYSTEM DECW$IGNORE_SHARED_ADDRESS TRUE If this is not done, and DECwindows is started after system startup has completed, the following error message will be displayed: -INSTALL-E-NOGHRES, insufficient memory in the code or data granularity hint region o When running on OpenVMS Alpha V6.2 or later, DECwindows Motif V1.2-3 installs five shareable image with shared linkage sections. Using shared linkage sections reduces the use of physical memory and improves performance. However, the images provided in DECwindows Motif V1.2-3 do not take full advantage of the shared linkage section feature. To correct this problem, this remedial kit includes new versions of the following shareable images: SYS$SHARE:DECW$XLIBSHR.EXE SYS$SHARE:DECW$XTLIBSHRR5.EXE SYS$SHARE:DECW$XMLIBSHR12.EXE SYS$SHARE:DECW$MRMLIBSHR12.EXE SYS$SHARE:DECW$DXMLIBSHR12.EXE The remedial kit replaces all five of these images. Replacing some of the images but not others, or installing any other DECwindows images with shared linkage enabled, may result in a system crash. Note that SYS$SHARE:DECW$TRANSPORT_COMMON.EXE, which ships with the X11 display server as part of the OpenVMS Alpha kit, is also installed with shared linkage. Refer to the DECwindows Motif V1.2-3 for OpenVMS Release Notes for additional information on shared linkage sections. o Because the images on the remedial kit were linked with version T11-11 of the linker, which supports shared linkage sections, ANALYZE/IMAGE will issue the following warning message for these images on OpenVMS Alpha V1.5: *** Reserved flag bit 12 is set. These warnings may be ignored. Login Problems: o In DECwindows Motif V1.2-3, remote logins often fail when the server and client are running different versions of OpenVMS, and if the DECW$LOGIN.LOG file is enabled the error message "[_XDispatchEvent - entered in reply state]" is written to the log file. For example, the remote login will fail if the client system is an Alpha system running DECwindows Motif V1.2-3 and OpenVMS Alpha V6.1 and the X11 display server is a VAXstation running OpenVMS VAX V6.1, but it would succeed if the client system were running OpenVMS Alpha V1.5. o In DECwindows Motif V1.2-3, there is a problem with "detached login failure" being periodically broadcast to the console after an unsuccessful login attempt. This is because the DECW$LOGINOUT process is restarting after it exits, even if the NORESTART flag is set in its WSA device, and because WSA devices are not being deleted. This problem is corrected so that DECW$LOGINOUT will not restart if the NORESTART flag is set, and it will delete WSA devices when they are no longer needed. To prevent DECW$LOGINOUT from deleting its WSA device before exiting, define the logical name DECW$LOGIN_PRESERVE_WSA in LNM$SYSTEM_TABLE with a value of TRUE. Session Manager and FileView Problems: o In DECwindows Motif V1.2-3, the Session Manager will terminate with an ACCVIO when the user tries to convert one of the color mixer pulldown menus into a tear-off menu in the Window Color dialog box. Because tear-off menus are not supported for option menus, with this ECO applied, these menus can no longer be made tear-offs. Workaround: Edit the DECW$SYSTEM_DEFAULTS:VUE$MASTER.DAT file and add the following line to the end of the file: VUE$MASTER*DXmColorMix*XmRowColumn.tearOffModel: XmTEAR_OFF_DISABLED o In DECwindows Motif V1.2-3, if the user has insufficient privilege to access a directory, FileView gives a directory listing of the previous directory. This can lead to problems if the user thinks the listing is for the directory specified in the file filter. o When a user logs into DECwindows for the first time after the machine has been upgraded from DECwindows XUI to DECwindows Motif V1.2-3, the login process hangs and the screen remains gray with a watch cursor. The user's DECW$*.DAT resource files are converted from XUI to Motif, so after restarting DECwindows with @SYS$MANAGER:DECW$STARTUP RESTART, the same user can log in successfully. This problem is corrected so that the initial login after upgrading from DECwindows XUI will be successful and it will not be necessary to restart DECwindows. Workaround: Make certain that the file DECW$SM_GENERAL.DAT does not exist in the user's SYS$LOGIN: directory. o In DECwindows Motif V1.2-3, on some monitors application windows are clipped, i.e. the windows are too large to fit on the screen. To fix this problem, the ECO kit defines the following resource in DECW$SYSTEM_DEFAULTS:DECW$SMB_WINDOW.DAT, so that it will affect all applications: *DXmfitToScreenPolicy: AS_NEEDED Defining this resource causes the Motif toolkit to put scroll bars on any window that will not fit on the screen. Workaround: Edit DECW$SYSTEM_DEFAULTS:DECW$SMB_WINDOW.DAT and add the resource definition. It's also possible to define the resource for a single user, e.g. by editing the user's DECW$XDEFAULTS.DAT file. DECterm Problems: o In DECwindows Motif V1.2-3, when running on some field test versions of OpenVMS, the CREATE/TERMINAL command fails to create a DECterm window if a node number is specified instead of a node name in the /NODE qualifier to SET DISPLAY, and DECnet is used as the transport. This was most apparent when using eXcursion to access a system running DECwindows Motif V1.2-3 on a field test version of OpenVMS (e.g., OpenVMS VAX T6.2-FT3). Workaround: Use the node name and not a node number when creating the display. In the case of eXcursion, it is possible to modify the PCX$SERVER.COM file to convert the node number into a node name before creating the display. o In DECwindows Motif V1.2-3, if DECterm is set to 8-bit controls in the Options->General dialog box, then the SET TERMINAL/INQUIRE command fails with a "-SYSTEM-F-BADPARAM" error. This problem only occurs on OpenVMS V6.2 or above due to recent changes in the SET TERMINAL/INQUIRE command. Workaround: To work around this problem, set DECterm to send 7-bit controls in the Options->General dialog box. o In DECwindows Motif V1.2-3, when printing multiple jobs in succession with printer controller mode, some jobs may not print at all. This problem was very apparent when printing a mail message from ALL-IN-1 with multiple attachments. Workaround: The workaround is to wait until one print job has completed before starting the next one, but that is not always possible as in the case of ALL-IN-1 printing a mail message with multiple attachments. DECimage Application Services (DAS) Problems: o In DECwindows Motif V1.2-3, compressed color .DDIF image files will not display in the CDA Viewer. Workaround: Decompress the image first using IMAGE VIEW command (if DAS is installed), and view the uncompressed version. Otherwise, no workaround is available to view compressed color .DDIF images using the CDA viewer. o In DECwindows Motif V1.2-3, the CDA Viewer leaves four files behind if an image is being viewed, in the application's current working directory: AFTER_SCALE.DDIF AFTER_SCALE.DMP BEFORE_SCALE.DDIF BEFORE_SCALE.DMP These files will also be left behind by any image viewing application linked to IMG$SHRLIB.EXE or IMG$SHRLIB12.EXE, which calls an IDS widget or hardcopy rendition function, if the image needs to be scaled. These files are no longer created after the ECO kit has been installed. Workaround: None. However, these files may be deleted at any time. o On Alpha systems, when running DECwindows Motif V1.2-3, Paint ACCVIOs when the picture size is set to 300 dpi and "Full View" is selected from the options menu. This error occurs when the process runs out of memory. When the remedial kit has been installed on the system, a Paint error-handler message box will be displayed in this situation. Bitmap File Problems: o In DECwindows Motif V1.2-3, the following bitmap files contain null characters at the end of each file. This results in compilation errors when compiling C++ programs. All the files are in SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]: HLINES2.XBM LEFT_PTR.XBM LEFT_PTRMSK.XBM LIGHT_GRAY.XBM MENU8.XBM OPENDOT.XBM OPENDOTMASK.XBM RIGHT_PTR.XBM RIGHT_PTRMSK.XBM ROOT_WEAVE.XBM SCALES.XBM STAR.XBM STARMASK.XBM STIPPLE.XBM TARGET.XBM TIE_FIGHTER.XBM VLINES2.XBM WEIRD_SIZE.XBM WIDE_WEAVE.XBM Workaround: Edit the files and remove the null characters. Xm Library 1.2.3 Problems: o In DECwindows Motif V1.2-3, when inserting one character in overstrike mode in an XmText or XmTextField widget, two characters are replaced. o In DECwindows Motif V1.2-3, when attempting to cascade to the right by dragging the mouse through a series of cascade buttons, the second cascade button sometimes arms (i.e., becomes depressed) without posting the next pulldown menu. If the cascades are posted by a series of MouseButton1 (MB1) clicks they are posted correctly. The menu is also posted correctly if the user disarms the cascade by moving the mouse off of the cascade, and then drags the mouse back onto the cascade. Workaround: Use mouse clicks to navigate cascade buttons in place of dragging the mouse. o In DECwindows Motif V1.2-3, repeated calls to XmGetPixmap cause a BadValue error in XCopyPlane when the pixmap is updated as a background XmNlabelPixmap in a widget. The error reported is: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 63 (X_CopyPlane) Value in failed request: 0x200 Serial number of failed request: 92 Current serial number in output stream: 93 o In DECwindows Motif V1.2-3, inserting text into an XmText widget with XmTextInsert does not correctly update the insert cursor position. The insert cursor position stays at its previous location. Workaround: The XmTextSetInsertPosition routine may be used to manually set the insert cursor position. o In DECwindows Motif V1.2-3, when the user holds down mouse button one (MB1) and drags the pointer through a menu hierarchy, dragging the pointer into a cascade button then causes the associated submenu to be pulled down. If an item is selected in that submenu, and the pointer is dragged through the menu hierarchy with MB1 held down, the submenu can no longer be pulled down when the pointer enters the cascade button. Workaround: While still holding down MB1, drag the pointer outside the "stuck" cascade button and then back inside it. The submenu should then be pulled down. o In DECwindows Motif V1.2-3, horizontal resize of a window forces a resize of the height of XmFrame children. In the following example, the widget hierarchy consists of: XmForm +-------------------+-------------------+ XmRowColumn XmRowColumn XmRowColumn | | | XmPushButton XmFrame XmFrame | | XmDrawingArea XmDrawingArea When the mwm resize handle is grabbed and the Form is expanded horizontally, then the XmFrame (and hence the XmDrawingArea) height decreases unexpectedly. o Several memory leaks in the DECwindows Motif V1.2-3 version of the Xm toolkit are fixed. o If an OpenVMS application running under DECwindows Motif V1.2-3 displays a File Selection Box (FSB) to an X11 display server using the Common Desktop Environment (CDE), the List boxes in the FSB will display incorrect directory and file names. o There is a performance problem in the XmText widget in DECwindows Motif V1.2-3 when displaying multibyte compound strings. This problem also results in mixed single and double byte strings being displayed incorrectly. DXm Library 1.2.3 Problems: o In DECwindows Motif V1.2-3, a memory leak occurs when issuing the following series of routine calls: DXmSvnDisableDisplay followed by DXmSvnInvalidateEntry followed by DXmSvnEnableDisplay. UIL Compiler 1.2.3 Problems: o In DECwindows Motif V1.2-3, if a UIL file contains a pulldown menu that contains nested cascade/pulldown pairs more than three levels deep, the UIL compiler sometimes generates a fatal error. The error message is: %UIL-F-SUBMIT_SPR, internal error - submit software problem report Workaround: The UIL compiler does not have a problem if the nested cascade/pulldown pairs are named. o In DECwindows Motif V1.2-3, the UIL compiler has a problem compiling RGB color values. This problem is corrected so that the inline color tables in a UIL file are disallowed and flagged with an error message. o In DECwindows Motif V1.2-3, the XmText ScrolledText resource set resources are not available in UIL. The ScrolledText Resource set is only valid when an XmText widget is the child of an XmScrolledWindow. The WML source files (and compiled WMD files) supplied with DECwindows Motif V1.2-3 do not contain the resource definitions for the XmText ScrolledText Resource Set. Attempting to use these resources (which are valid only when an XmTextwidget is created in an XmScrolledWindow) results in the following UIL compiler error: XmNscrollHorizontal = false; * %UIL-W-UNSUPPORTED, the XmNscrollHorizontal argument is not supported for the XmText object Workaround: Edit DECW$SYSTEM_DEFAULTS:DECW$UIL_DXM_MOTIF.WML and DECW$UIL_OSF_MOTIF_1_1.WML to add these resources. Motif Window Manager (mwm) 1.2.3 Problems: o In DECwindows Motif V1.2-3, the text in an inactive ICON label is slightly off center and the text in an active ICON label is truncated to the right. Neither of these problems existed with the Window Manager in DECwindows Motif V1.1. o When an application built on DECwindows Motif V1.1 is displayed on a system running the DECwindows Motif V1.2-3 window manager and creates an XmDIALOG_SYSTEM_MODAL dialog as the first widget to be displayed for that application (as as a login dialog box), the window manager hangs the system in a System Modal condition and will not release the server grab. Workarounds: There are two workarounds. The first is to change the modality of the dialog box from XmDIALOG_SYSTEM_MODAL to XmDIALOG_FULL_APPLICATION_MODAL. This will provide some amount of restriction on the user without hanging the server. The second work-around is to build the application under Motif V1.2 and display it on a Motif 1.2 system. If this is done, then there is no problem with using XmDIALOG_SYSTEM_MODAL. Xm Library 1.1.3 Problems: o In DECwindows Motif V1.2-3, applications linked with the 1.1.3 Xm toolkit sometimes terminate when the user performs keyboard traversal on pulldown menus. o In DECwindows Motif V1.2-3, in applications linked with the 1.1.3 toolkit, an XmList widget will flicker when it is updated with calls to XmListReplaceItemsPos() in rapid succession. o In DECwindows Motif V1.2-3, in applications linked with the 1.1.3 toolkit, XmList widgets are not displayed correctly in a Right to Left direction. o In DECwindows Motif V1.2-3, in applications linked with the 1.1.3 toolkit, XmCascadeButton widgets are not displayed correctly on multi-head systems. To correct this problem, a screen field has been added to the XmArrowPixmap structure. o In DECwindows Motif V1.2-3, applications linked with the 1.1.3 toolkit which contain very large compound strings terminate with an ACCVIO status because of an array overflow. o In DECwindows Motif V1.2-3, ORACLE[R] applications can terminate with an ACCVIO status due to traversal problems. o In DECwindows Motif V1.2-3, applications linked the 1.1.3 can terminate with an ACCVIO status due to problems in traversal when destroying widget hierarchies. o In DECwindows Motif V1.2-3, a memory leak can occur when using the XmTextField widget in an application linked with the 1.1.3 toolkit. o In DECwindows Motif V1.2-3, Notepad becomes compute bound after the user modifies a file and selects "Save" from the File menu, because of a problem in the 1.1.3 XmText widget. o There is an Xm 1.1.3 toolkit access violation problem which was introduced in the Motif ECO 07 patch kit to DECwindows Motif V1.1. DXm Library 1.1.3 Problems: o There is a memory leak in the 1.1.3 DXmSvn widget in DECwindows Motif V1.2-3. o There is a problem with 1.1.3 DXmCSText scrolling in DECwindows Motif V1.2-3 when Right to Left direction is selected, and a segment splits exactly at the end of the line. o There is a problem in DECwindows Motif V1.2-3 where the 1.1.3 DXmCSText will hang if more than three lines of TAB characters are typed. Xt Intrinsics Library R4 Problems: o There is a problem in the R4 version of XtPhase2Destroy in DECwindows Motif V1.2-3 which can cause an ACCVIO when XtDestroyWidget() is called to destroy relatively large widget hierarchies. o There is a problem in DECwindows Motif V1.2-3 with applications that are linked with the Xt R4 Intrinsics Library where occasionally passive grabs are not ungrabbed when the widget is destroyed. Xlib Problems: o In DECwindows Motif V1.2-3, Xlib disables user mode ASTs on Alpha systems, even if they were previously enabled. o In DECwindows Motif V1.2-3, there are a number of Non-C bindings (X$ calls) that do not work properly. Many of them can cause an ACCVIO that is not the fault of the application developer. INSTALLATION NOTES: If you are installing this kit on OpenVMS Alpha V6.2 or later and did not disable the use of shared linkage sections before starting DECwindows by defining the logical name DECW$IGNORE_SHARED_ADDRESS to TRUE, you will need to reboot the system after installing this kit. If you are not rebooting the system, you will need to start the X11 server in order to make use of the fixes within this remedial kit. This can be done by issuing the following command after the installation is complete: @SYS$MANAGER:DECW$STARTUP RESTART [R] Motif, OSF, and OSF/Motif are registered trademarks of the Open Software Foundation, Inc. [R] ORACLE is a registered trademark of Oracle Corporation.

This patch can be found at any of these sites:

Files on this server are as follows:

alpmotf08_u3012.README
alpmotf08_u3012.CHKSUM
alpmotf08_u3012.CVRLET_TXT
alpmotf08_u3012.a-dcx_axpexe