![[Return to Library]](BOOKSHELF.GIF)
![[Contents]](TOC.GIF)
![[Previous Chapter]](REW.GIF)
![[Next Section]](NEXT.GIF)
![[Next Chapter]](FF.GIF)
![[Index]](INDEX.GIF)
![[Help]](HELP.GIF)
This chapter contains notes about issues and known problems with the windowing software and, whenever possible, provides solutions or workarounds to those problems. The following topics are discussed in this chapter:
The following notes apply to graphics hardware restrictions.
![[Previous Section]](PREV.GIF)
This section provides information about how configure a CalComp DrawingBoard III tablet, an input device supported by the Xinput extension to the Xserver. Once the software for the tablet is installed on your system, you can configure it to emulate a system mouse.
If you intend to use the CalComp DrawingBoard III tablet software, you
must edit
/usr/var/X11/Xserver.conf
to turn on support for the X Input extension. To do this, remove the
comment characters surrounding the following lines. The backslash in this example indicates line continuation and is not in the actual display:
input < < _dec_xi_db3 lib_dec_xi_db3.so XiDb3Init /dev/tty00:1:12:12:16:\ 1:8:1000:1:1 > >
You should also review these lines to ensure that the options specified for the tablet are correct, especially the tty that is specified as the serial port where the tablet is connected to your system.
The last line of this file has the following syntax. The backslash in
this example indicates line continuation and is not in the actual
display:
device:mode:tabletWidth:tabletHeight:numbtns:corePointer:mouseScale:\
resolution:Xincrement:Yincrement
Table 5-1 can help you determine how to set up the entries for the tablet in the /usr/var/X11/Xserver.conf file.
| Option | Description |
| device |
The port
(tty)
to which the device is connected.
The default is tty00. |
| mode | This should be set to 1 for absolute motion. |
| tabletWidth |
Width of the active tablet area in inches, not the physical size.
The default is 12. |
| tabletHeight |
Height of the active tablet area in inches, not the physical size.
The default is 12. |
| numbtns |
Number of buttons on the puck or pen.
The maximum number is 16 and the default is 16. |
| corePointer |
0 indicates a native tablet mode (no system mouse).
1 indicates emulate core pointer (the mouse and tablet are both core pointer devices. The default is 1 (emulate core pointer). |
| mouseScale |
1 to 50 scaling factor in relative mode. Determines the speed of the
cursor; the higher the number, the slower the cursor moves.
The default is 8. |
| resolution |
1 to 2540 lines per inch (lpi).
The default is 1000. |
| Xincrement |
How much the X axis must be incremented to cause the tablet to send new
coordinates to the Xserver. The range is 0 to 65536.
The default is 1. |
| Yincrement |
How much the Y axis must be incremented to cause the tablet to send new
coordinates to the Xserver. The range is 0 to 65536.
The default is 1. |
The device option is required and specifies which tty device should be associated with the tablet. By default, the installation software assigns the CalComp DrawingBoard III tablet to tty00, which you may want to change if that tty is already allocated. For information on how to determine which serial port your tablet is connected to, see the hardware documentation that was shipped with your processor.
Note that when the stylus or puck is moved as far as the minimum Xincrement or Yincrement value, the value of the corresponding axis is updated. For example, if the Xincrement value is set to 10 and the tablet is moved 10 units along the X axis, the value of the Y axis will also be updated simultaneously with the X axis, even if the Yincrement value has not been reached. Keep this in mind when setting the Xincrement and Yincrement options.
After you have configured the /usr/var/X11/Xserver.conf file, you must follow these steps to turn on support for the tablet in the Xserver:
#
/usr/sbin/shutdown -r +5 "Turning on support for the Calcomp \ Drawingboard III tablet"
When the system comes back up, the tablet will be configured into the Xserver and ready to use.
When the Xserver first accesses the tablet, it performs some hardware-specific initialization that can be saved in the on-board memory of the tablet. To save these settings, follow these steps:
The following notes and restrictions apply to the CalComp DrawingBoard III tablet.
Different versions of Qvision demonstrate fillsolid drawing problems, leaving a line at the bottom of the screen, which is evident when running CDE blank lock screen. The line varies in color and intensity depending on the version of the Qvision board.
The following notes apply to X servers.
The windowing system on AlphaStation 600 systems may experience poor response times in a heavy paging environment. This problem occurs on all platforms, but is most pronounced on AlphaStation 600 series processors. Mouse movement is unaffected, but windowing operations such as exposing a window may be degraded. When this condition occurs you may not be able to use telnet or rlogin. The poor response period may be greater than 2 minutes or it may stop after a few seconds. The cause is usually a memory intensive application that depletes the number of available pages on the free list to an absolute minimum. When this occurs, only privileged tasks are able to access any free pages. All other tasks are blocked, most notably the window manager. To verify if your system is experiencing this problem, open a terminal with xterm while your memory-intensive application is running and enter the following command:
#
vmstat 2
The output from this command will show the number of free pages available under the heading free. If this number falls below the reserved amount vm-page-free-reserved, your system is exhibiting the memory problem. The following is sample output on a machine experiencing this condition:
Virtual Memory Statistics: (pagesize = 8192) procs memory pages intr cpu r w u act free wire fault cow zero react pin pout in sy cs us sy id 2 37 15 5832 4021 1108 20K 5975 4575 285 4761 0 62 196 266 1 1 98 2 37 15 5851 4002 1108 99 13 50 0 8 0 4 13 239 0 1 99 3 37 15 7039 2788 1134 26 0 26 0 0 0 17 51 255 1 9 90 3 37 15 9791 10 1140 7291 17 7258 0 13 48 288 12 422 1 68 31 3 37 15 9790 9 1149 1049 0 1048 39 1 146 472 15 527 0 32 68 3 36 15 9784 9 1116 743 0 741 0 2 106 446 12 466 0 22 78 3 36 15 9811 9 1096 460 0 459 0 1 107 434 12 459 0 20 79
In this example, vm-page-free-reserved is set to its default value of ten pages and the VM subsystem has been overwhelmed. The system will demonstrate degraded window performance and other performance degradations. If the output from vmstat on your machine does not exhibit similar results, do not tune your system as Digital recommends in this note.
An interim solution to this problem is to:
Make the changes to three tuning parameters in the /etc/sysconfigtab file as described in the next paragraph.
Digital recommends that you systematically double the parameter values until you reach an acceptable balance between user interactivity and application performance. The following parameter values provide reasonable interactivity with moderate performance degradation on a Alphatop Station 6000 with 128M of physical memory These changes are intended to keep a larger than normal number of pages on the free list as a buffer:
This value enables the system to start paging earlier than usual.
This value enables the system to stop paging later than usual.
This value enhances the swapping of tasks to force the memory intensive application to be swapped out occasionally.
You must reboot your system after making these changes.
You may find that your system performs acceptably with some manipulation of these parameters. However, these suggested tuning parameters were devised to provide some level of user interactivity in a heavy paging/swapping environment. They may not be the best solution for your particular needs, but may provide a reasonable starting place.
If your system does not have 128MB of memory, reduce the suggested numbers. The units for these values are pages (which are 8KB) resulting in a substantial 32MB of memory use. If you are uncertain, try doubling the default parameter values until you reach acceptable perfromance. You can check the default values using dbx on a running system as follows:
# dbx -k /vmunix (dbx) p vm_page_free_target 2048 (dbx) p vm_page_free_optimal 1029 (dbx) p vm_page_free_min 20 (dbx) p vm_page_free_reserved 10
Refer to the System Tuning and Performance Management manual for information on these parameters and system tuning in general.
To raise the priority of the window manager, open a terminal window and find the process ID of the window manager found using the ps command. Stop the window manager process with the kill command.
Restart the window manager using nice as follows:
#
nice -2 dtwm &
IN this example, replace dtwm with mwm or twm if you are using a different window manager. If your system is tuned correctly, there should be is a small latency when the memory intensive application starts, which will balance as the memory subsystem recovers. You should be able to expose windows and drag them around with a reasonable response time. If you expose a window that has not been used for some time, expect some latency. This is because you are now working in a heavy paging/swapping environment and those pages are not yet available.
To avoid system panics after modifying the sysconfigtab file, you must use this release of Digital UNIX. Keep in mind, you will need to kill and restart the window manager each time you terminate your xsession. Note that to use nice, you need to be a privileged (root) user.
CDE provides limited support for X servers with more than one screen. While a multiscreen environment is possible, a number of inconsistencies are noticeable. For example, colors in secondary screens may not be correct, icons may not display properly, and applications may not appear on the screen where they are invoked. Digital is currently working with OSF to resolve issues related to multiscreen environments for future releases of CDE.
If you use the Keyboard Options desktop application /usr/dt/bin/dxkeyboard, to change the keymap, X11R5 clients will not be notified of the change. For example, a dxterm running on DEC OSF/1 Version 3.2 displaying to a Digital UNIX Version 4.0 system will not be notified that the keyboard mapping changed.
To avoid this problem, enter the following command after using dxkeyboard to change the keyboard mapping:
xmodmap -e "keycode 248 = NoSymbol"
The final revision of the X Keyboard Extension, XKB Version 1.0, will be different from XKB Version 0.65, shipping with this release. The format of /usr/lib/X11/xkb/keymaps.dir will change. Do not modify this file as it will not be preserved with future updates of the operating system.
To force the server to use a specific XKB keymap, add the -xkbmap option to the server options line in /usr/lib/X11/Xserver.conf. Refer to the reference page on Xdec for more information.
Some versions of Interleaf running under Digital UNIX exhibit display anomalies when manipulating Interleaf PullDown or PopUp menus. This will appear as a section of the screen that is not correctly repainted when the menu is removed.
This is due to a problem with Interleaf in relying on the contents of a Save-Unders region without responding to expose events. The problem may be fixed in a later version of Interleaf but can also be eliminated by disabling Save-Unders on the X Server command line. Do this by editing the /var/X11/Xserver.conf file to add the -su argument to the args statement. Refer to the Xdec(1X) reference page for the exact syntax.
The following notes apply to X clients.
Color rich applications, such as Netscape, exhaust a large number of colormap resources. This results in problems with other graphical applications. For example, you may notice that icons normally displayed by the CDE Application Manager are not displayed when a color rich application is currently running on the system. Graphics displayed by applications and online help volumes may also be affected. The icon editor, dticon, may not be able to open a pixmap that contains a large number of colors.
In most cases this is a visual problem, and it may not be necessary to take any corrective actions. The CDE icon labels can be used in the same way as the icon for user actions such as drag-and-drop, single and double click.
The simplest solution is to exit the color rich application. There are several alternate actions:
Netscape*maxImageColors: 96
A new resource definition (*DXmfitToScreenPolicy: AS_NEEDED) has been added to the /usr/lib/X11/app-defaults/DXnotepad resource file for the C locale.
If you are doing an update installation, this new resource is not automatically merged into your existing /usr/lib/X11/app-defaults/DXnotepad file. Therefore, you must manually manually append the following text to your C-locale DXnotepad resource file:
*DXmfitToScreenPolicy: AS_NEEDED
This definition tells the toolkit to add scroll bars to a dialog box if the dialog box does not fit on the screen. It is required to support new workstations with smaller monitor resolutions.
MH and dxmail default to using lockf for locking mailboxes. This differs from the default used by both binmail and mailx. This is not a problem unless NFS is used to share mailbox directories (for example, /var/spool/mail and $HOME/Mail). If NFS is used, then the lock style should be explicitly set. See the mail_manual_setup(7) reference page for more information.
When dxmail is run using a new locale setting, mail subjects in the mail folders are still encoded in the codeset used by the previous locale. Non-ASCII characters in these subjects will be displayed incorrectly.
To correct this, use the rescan mail folder function to convert all existing subjects lines to the codeset used by the new locale.
MH and A Motif clipboard interoperability problem prevents applications from exchanging clipboard data with applications from releases prior to DEC OSF/1 Version 3.0. This break in compatibility was necessary to restore clipboard interoperability between Digital UNIX and 32-bit architectures.
To work around this problem, use the quick copy function to transfer data. Quick copy is normally performed by selecting the text to be transferred and then clicking MB2 in the paste location. dxmail default to using lockf for locking mailboxes. This differs from the default used by both binmail and mailx. This is not a problem unless NFS is used to share mailbox directories (for example, /var/spool/mail and $HOME/Mail). If NFS is used, then the lock style should be explicitly set. See the mail_manual_setup(7) reference page for more information.
Hilite Mouse Tracking is disabled by default. See the xterm(1X) reference page for information on how to reenable this feature.
Motif applications built on a release of Digital UNIX prior to v2.0 rely on the Motif 1.1.3 libraries. These retired runtime libraries are no long installed by default. These libraries are to be found in subset OSFMOTIF11400.
If an application that relies on these retired libraries is executed, it will fail with an error message. For example:
#
xmosaic
This command produces an error message similar to the following:
1166:/usr/local/bin/xmosaic: /sbin/loader: Fatal Error: object libXm.so from liblist in /usr/local/bin/xmosaic has version , which does not match the found object: /usr/shlib/libXm.so (with version "motif1.2")
If /usr/sbin/xsetup is used to switch login environments from the CDE to XDM, it may need to install the subset OSFOLDX11400 to regain the expected user environment. If this subset is missing, the default X session will consist of a single xterm and the twm window manager instead of the more familiar Digital session manager.
The following notes apply to CDE clients.
File Manager, Application Manager and Trash Manager are different views supported by the dtfile application. Avoid invoking dtfile from a remote system with the environement variable DISPLAY set appropriately. This is because of the client-server model used by the dtfile application and its close interaction with the tooltalk messaging system.
In the event of an unexpected behaviour from any of these utilities, please close down all windows associated with the File Manager, Application Manager and Trash Manager. Then kill all processes associated with dtfile. You can get the pid for each process using the following command line:
#
ps -aef | grep dtfile
When using enhanced security, Autopause does not allow you to resume a suspended CDE session.
If you are not logged in as root, the dtsession Autopause and Locking features will not unlock. The session must be unlocked either by typing the root password or remotely killing the dtsession process, terminating and restarting the session.
The dxpause program exhibits the same behavior and there is no workaround for this problem. To avoid the problem, turn off the Screen Lock toggle on the Style Manager menu, Screen option.
the dtmail utility does not honor the user configurable mail locking environment variable MAILLOCKING. If you are using NFS, you must have nfs locking enabled on both client and server systems.
DtMail will disable tooltalk locking by default. To enable it, select the following option from the Mail Options->Advance dialog box:
Use network aware mail file locking
Alternatively, set the following option in your $HOME/.mailrc file:
cdenotooltalklock='f'
If tooltalk locking is enabled, and the rpc.ttdbserverd daemon is not running, you will get the following message:
Mailer is unable to obtain exclusive access to this mailbox because the system is not responding.
For this time only, you can choose to open this mailbox read-only, or to open it read-write without exclusive access (use only if no one else is using this mailbox).
You can either quit and start the rpc.ttdbserverd daemon, or click on read-write allowing you to continue without tooltalk lock.
Changing the values for rows and columns in the Mail Options->Message View will not take effect immediately when you click on OK or APPLY. Exit dtmail and restart it again from the control panel, command line, or file manager.
If you compose a mail message by selecting one of the following from the dtmail main window, attachments will not be included:
Include the attachments manually using the drag and drop feature.
Incorrect default permissions on /dev/zero prevent dtmail from starting.
You may see the following message when starting dtmail:
"No memory available for operation"
If you see this message, set the permission mode on /dev/zero to 666 as follows:
#
chmod 666 /dev/zero
The Common Desktop Environment (CDE) has a static dependency on the state of the network configuration. For more information, see Section 3.6.8.
CDE users should remove any xnlLanguage resource settings from their .Xdefaults files. Those settings are typically left over from one of the user's earlier DECwindows sessions, where the user selected a language from the session manager's language menu and then saved that setting.
The xnlLanguage settings should be removed because they override whatever language you select from the language menu in the CDE login window.
When logging in to the CDE desktop, it is possible that not all desired applications will be restarted. The X server process may not be able to handle all of the requests for new open connections causing some to fail in the XOpenDisplay call. Some applications, like xterm, will log startup errors, such as:
xterm error: can't open display :0
in the dxconsole window.
To avoid this problem, add the following resource to your $HOME/.Xdefaults file:
Dtsession*contManagement: 2
This resource enables a handshake protocol between the CDE session manager and window manager during the login phase to control the appearance of new windows. While it may marginally increase the time before the login completes, it better assures that all applications will be restarted.
For a multiuser system, this resource can be added to the /usr/dt/app-defaults/C/Dtsession file to make the change for all users automatically.
The following note applies to windows programming.
In the fonts Lucida-Typewriter-medium-R-normal, the glyphs for multiply (X) and divide (-:-) are reversed. The multiply is where the divide should be, and vice versa. If the representation of these glyphs are important to your application, use a different font.
The following notes apply to restrictions on use of internationalization features in the windowing environments.
Chinese DECterm software supports the use of DEC Hanyu, Big5 and DEC Hanzi as its terminal code. To process Taiwanese EUC codeset, users should do the following:
%
/usr/bin/X11/dxterm -xnl zh_TW.dechanyu
%
setenv LANG zh_TW.eucTW
%
/usr/i18n/bin/stty adec acode eucTW tcode dechanyu
After that, users can use terminal applications to process Taiwanese EUC files.
On PC-style keyboards, the Hanyu, Hanzi, Hangul and Kanji input servers use the Delete key instead of the Backspace key to erase information.
The Digital UNIX input servers for Hanyu, Hanzi, and Kanji support only X and local transports. Transports over DECnet and TCP/IP are not supported. DECnet and TCP/IP transports are available only for IM servers that have a single input-server atom name.
X11R6 input servers can connect to R4, R5 and R6 clients under the same locale. However, if the system is using multiscreen support, only R6 clients can be connected.
When the Language setting is zh_TW.big5, EDPC support must be turned off. Otherwise, random characters will appear in the candidate list for unsupported 4-byte encodings. Select the Input Method Customization... option from the Options button of the input server window in the lower left corner of your screen. Then in the customization dialog box, click the EDPC support button to off.
String conversion using XStringStyle() is not supported for interclient communication under the ja_JP.SJIS locale. This is because the X library assumes that the 7-bit string data has ISO8859-1:GL encoding, whereas the ja_JP.SJIS locale assumes the data has JISX0201.1979-0:GL encoding.
The new mdxbook command in the IOSWWOLDBKR400 subset is a variant of dxbook Version 3.0. Unlike dxbook, the mdxbook command supports printing files with Chinese and Korean characters.
The display quality of mdxbook is not as good as dxbook. Therefore, install mdxbook only if you need to print Chinese and Korean characters.
The following notes apply to Hebrew support.
HIM_ ALLOW_STATUSNONE
If XIMStatusNone is required but the variable is not defined, XIMStatusNothing will be used.
The environment variable ADECW_MOTIF12 is needed for the cut and paste operation of the DXmCSText to work properly in the Hebrew environment. If you encounter problems with the cut and paste operation of a mixed English/Hebrew/Numeric strings, use this workaround and define the variable in your working environment (the value is arbitrary).
Hebrew CDE users should avoid using the following CDE applications:
These applications can hang in the Hebrew locale because of problems in the Hebrew input method.
When the notepad application is started with off-the-spot input style, the input area attached at the bottom of the application disappears during split view and delete view.
The X server will automatically choose a keymap based upon the language and keyboard settings of the system console. If your locale is not available on the system console, or you wish for the server to load a different keymap, you must set the system default keyboard map. The default keyboard map is specified by adding the -xkbmap option to the args list in the /usr/var/X11/Xserver.conf file. Add the -xkbmap option using the following syntax:
! you specify command line arguments here args < -pn -xkbmap <keymap_file_name>_<keymap_name> >
For example:
-pn -xkbmap digital_japanese_lk411aj
The available keymap files are located in /usr/lib/X11/xkb/keymap, where there is one file for each locale. The individual keymaps for the locale are in the keymap file, and are specified by the keyword xkb_keymap. For example, the keymap file /usr/lib/X11/xkb/keymap/digital_japanese, contains an entry for the lk411aj keymap.
In addition, keymaps can be changed after logging in by running the Keyboard Options desktop application /usr/dt/bin/dxkeyboard if you are using CDE. Use the keyboard setting option of the session manager if you are using xdm.
The following instructions are for modifying some system files to allow for some support of Lithuanian and Slovene.
DX applications V4.0 do not support the use of mnemonics in Lithuanian and Slovene language variants.
For the Visual Differences application, /usr/bin/X11/dxdiff, to display differences between two text files written in Lithuanian or Slovene language you must do the following. Edit the resource file DxDiff located on /usr/lib/X11/app-defaults directory and change the following line:
*dxdiff*textdisplay*fontList: fixed
to:
*dxdiff*textdisplay*fontList: -*-terminal-medium-r-narrow--18-*-*-*-c-*-*-*
You need superuser (root) privileges to make this change.
Some DX applications that are not integrated as part of the CDE desktop, but can be invoked using the File Manager or command line, do not set all display fonts according to the locale in use. If users want these applications to provide full Lithuanian and/or Slovene language support, they must perform the following corrective actions on the system with Lithuanian and/or Slovene language variant installed.
Note that all these actions must be performed by superuser.
To use Lithuanian and/or Slovene national characters in dxmail, edit the resource file /usr/lib/X11/app-defaults/DXMail and change the following lines:
*outlineList*DXmfontListDefault: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *outlineList*DXmfontListLevel0: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *outlineList*DXmfontListLevel1: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *tocList*DXmfontListDefault: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *tocList*DXmfontListLevel0: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *Item.fontList: *-*-Helvetica-Bold-R-Normal--*-100-*-*-*-*-ISO8859-1 *XmText.FontList: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1 *Text.FontList: *-*-*-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1
to:
*outlineList*DXmfontListDefault: *-*-*-Medium-R-Normal--*-120-*-*-M-*-*-* *outlineList*DXmfontListLevel0: *-*-*-Medium-R-Normal--*-120-*-*-M-*-*-* *outlineList*DXmfontListLevel1: *-*-*-Medium-R-Normal--*-120-*-*-M-*-*-* *tocList*DXmfontListDefault: *-*-*-*-R-Normal--*-120-*-*-*-*-*-* *tocList*DXmfontListLevel0: *-*-*-*-R-Normal--*-120-*-*-*-*-*-* *Item.fontList: *-*-*-*-R-Normal--*-120-*-*-*-*-*-* *XmText.FontList: *-*-*-Medium-R-Normal--*-120-*-*-*-*-*-* *Text.FontList: *-*-*-Medium-R-Normal--*-120-*-*-*-*-*-*
To use Lithuanian and/or Slovene national characters in dxnotepad, edit the resource file /usr/lib/X11/app-defaults/DXnotepad and change the following line:
*textwindow.fontList: -*-Terminal-Medium-R-Narrow--*-140-*-*-C-*-ISO8859-1
to:
*textwindow.fontList: -*-Terminal-Medium-R-Narrow--*-140-*-*-C-*-*-*
In order to use Lithuanian and/or Slovene national characters in Bookreader bookshelf and book names, edit the resource file /usr/lib/X11/app-defaults/DXBookreader and change all occurences of string:
-*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1
to:
-*-*-*-R-Normal--*-120-*-*-P-*-*-*
The dxpaint Lithuanian and Slovene language variants do not support the insertion of Lithuanian and Slovene national specific characters.
The dxclock application displays date and time using english day/month abbreviations and format.
The dxcalendar application displays date and time using english day/month abbreviations and format.
To create calendar entries using Lithuanian and/or Slovene national specific characters, edit the resource file /usr/lib/X11/app-defaults/DXcalendar and change the following two lines:
*font_small_tb.fontList: \ -*-Menu-Medium-R-Normal--*-100-*-*-P-*-ISO8859-1 *font_medium_tb.fontList: \ -*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1
to:
*font_small_tb.fontList: -*-*-*-R-Normal--*-100-*-*-P-*-*-* *font_medium_tb.fontList: -*-*-*-R-Normal--*-120-*-*-P-*-*-*
In addition to the new default Common Desktop Environment (CDE), Digital UNIX V4.0 still supports DECwindows interface as an optional user interface. However, if you want to use the old DECwindows user interface you need to log in after selecting Dxsession session from Options --> Session menu of Digital UNIX login screen.
Lithuanian language variant users that wish to operate in Dxsession environment must specify the default user interface font by editing the file .Xdefaults located on their home directory and adding the following line and log in again:
*FontList: -*-*-*-r-Normal--*-120-*-*-*-*-*-*
If users operate in a multilingual user interface environment, this above corrective action will cause other language variants to display using the default font which is slightly different than to the font family used before this action was performed.
Users that wish to have the default user interface font to be used with the Motif window manager need to edit the resource file /usr/lib/X11/app-defaults/Mwm and change the following line:
Mwm*fontList: -*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1
to:
Mwm*fontList: -*-*-*-R-Normal--*-120-*-*-P-*-*-*
Note that this change must be performed by a superuser (root).