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:
Hardware notes and restrictions (Section 7.1)
X servers (Section 7.2)
CDE clients (Section 7.3)
Internationalization (Section 7.4)
7.1 Hardware Notes and Restrictions
The following notes apply to graphics hardware restrictions.
7.1.1 PowerStorm Graphics Support
Support for the following graphics adapters is not available on this version of Tru64 UNIX. Therefore, these devices are supported in VGA mode only:
PowerStorm 4D40T
PowerStorm 4D51T
PowerStorm 4D60T
PowerStorm 300
Please refer to the following URL for the necessary drivers and more information:
http://www.service.digital.com/open3d
7.1.2 Qvision Graphics Display Error
Different versions
of Qvision graphics boards demonstrate
fillsolid
drawing
problems, leaving a line at the bottom of the screen, which is evident when
running the CDE blank lock screen.
The line varies in color and
intensity depending on the version of the Qvision board.
7.2 X Servers
The following notes apply to X servers.
7.2.1 Limited Multiscreen Display Support with CDE
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.
Using the PanoramiX extension mitigates
some of these inconsistencies.
7.2.2 Pixmap Color Errors with PanoramiX
Some pixmap color corruption has been seen when using the PanoramiX extension. Background pixmaps can be corrupted when a client is displayed on any screen other than the physical screen 0. The corruption is most frequently seen when using Netscape and loading pages with background pixmaps.
To avoid this problem, check the "Always use my colors, overriding document."
box under the color section of Netscape preferences.
7.2.3 Using LBX Clients
This note provides information for using LBX clients:
On systems without DECnet, you must start the
lbxproxy
with the
-pn
option.
You do not use the X server's node-based access control (xhost
host_name) for LBX clients.
XDM-AUTHORIZATION-1 authorization only works for LBX clients
if the client is running on the same system as the
lbxproxy
that it is using and if the client specifies a network connection to
lbxproxy
(lbxproxy -display
host_name:1) instead of a local connection (lbxproxy -display :1).
Note that the restrictions on authorization for LBX clients are part of the standard implementation of LBX from The Open Group.
You can use the following methods to authorize an LBX client to display on an X server:
Use MIT-MAGIC-COOKIE-1 authorization. You can do this by including the MIT-MAGIC-COOKIE-1 entries in the LBX client's XAUTHORITY file.
Use XDM-AUTHORIZATION-1 authorization and run a separate
lbxproxy
on each client system that is used by the clients on that
system.
Also, set the clients' display specifications to use a network
connection to
lbxproxy
(lbxproxy
host_name:1).
Disable access control in the X server.
You can do this by
starting the X server with the
-ac
options or by using
the
xhost +
command.
These methods are insecure and are
not recommended.
If you use the MIT-MAGIC-COOKIE-1 or XDM-AUTHORIZATION-1 authorization
methods with an LBX client, the client's XAUTHORITY file entries must
specify the display name for the
lbxproxy
utility and the
authorization key for the target X server.
The following are some examples of using LBX. In these examples, server is the system running the X server, client1 is one system running LBX clients, and client2 is a second system running LBX clients.
If the following command is executed on client1, the
lbxproxy
listens for connections on client1:1 and displays information
on server:0.
#lbxproxy -pn -display server:0 :1
LBX clients running on client1 that are not using XDM-AUTHORIZATION-1 authorization should set their display to :1. For example:
#xterm -display :1
LBX clients running on client1 that are using XDM-AUTHORIZATION-1 authorization should set their display to client1:1. For example:
#xterm -display client1:1
All LBX clients on client2, regardless of whether they are using XDM-AUTHORIZATION-1 authorization, should set their display to client1:1.
To use the MIT-MAGIC-COOKIE-1 or XDM-AUTHORIZATION-1 authorization mechanisms, set up your XAUTHORITY files as follows:
The X server's XAUTHORITY file:
server:0 MIT-MAGIC-COOKIE-1 0123456789abcdef0123456789abcdef server/unix:0 MIT-MAGIC-COOKIE-1 0123456789abcdef0123456789abcdef
The XAUTHORITY file for
lbxproxy:
server:0 MIT-MAGIC-COOKIE-1 0123456789abcdef0123456789abcdef server/unix:0 MIT-MAGIC-COOKIE-1 0123456789abcdef0123456789abcde
The LBX clients' XAUTHORITY files (on both client1 and client2):
client1:1 MIT-MAGIC-COOKIE-1 0123456789abcdef0123456789abcdef client1/unix:1 MIT-MAGIC-COOKIE-1 0123456789abcdef0123456789abcdef
7.2.4 Colons Missing from Display
In a few instances, colons are seen as spaces in a display after
you create a cluster.
This problem is rare and does not affect the files.
To correct the problem, log out and log back in to the session.
7.3 CDE Clients
The following notes apply to CDE clients.
7.3.1 Inaccessible Dialog Buttons
When
running CDE with 640 x 480 graphics resolution, the OK, Apply, Cancel, and
Help buttons of some application dialogs may be inaccessible.
To correct this
problem, set the
DXmfitToScreenPolicy
resource to
as_needed
in the application's defaults file or, for systemwide
problems, in the
/usr/dt/config/$LANG/sys.resources
file.
7.3.2 Screen Savers Prevent Efficient Power Management
When the screen on a DPMS-capable monitor is switched to standby, suspend, or off mode, the X server continues to run the screen saver. In CDE, which has a number of active screen savers, this may defeat the CPU slowdown features for power management on certain Energy Star-compliant platforms. To minimize power consumption, you should stop using active screen savers by doing any of the following:
In the Screen Saver panel of the Screen dialog box, under the Style Manager, select Blank Screen and deselect any active screen savers that might be running.
Click on the Off button in the same dialog box.
Execute
xset s off
from a terminal client
window.
7.3.3 Remote Invocation of CDE File Manager dtfile
File
Manager, Application Manager, and Trash Manager are different views supported
by the
dtfile
application.
Avoid invoking
dtfile
from a remote system with the
DISPLAY
environment
variable set appropriately.
This restriction is necessary because of the
client-server model used by the
dtfile
application and
its close interaction with the ToolTalk messaging system.
In the event of unexpected behavior from any of these utilities, close
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 by using the following
command:
#ps -aef | grep dtfile
7.3.4 Possible Failure in the XOpenDisplay Call
When logging in to the CDE desktop, some applications may not
restart.
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, log startup
errors in the
dxconsole
window, such as the following error:
xterm error: can't open display :0
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.
You can add this to the
/usr/dt/app-defaults/C/Dtsession
file to make the change for all users automatically.
7.3.5 Login to CDE_SESSION Restriction
Login to
CDE_SESSION
is restricted to machines
with host names that are not greater than 31 characters.
This
is because CDE and the X libraries use the
uname
command
to get the system name to process the user credentials.
7.4 Internationalization
The following notes apply to restrictions on use of internationalization
features in the windowing environments.
7.4.1 Japanese Keyboard Support in Console Mode
When running in single-user or console mode, Tru64 UNIX now supports two new Japanese keyboard types (JIS and ANSI) on AlphaStation and AlphaServer systems. (Japanese keyboard support is not available on TURBOchannel-based machines.)
To use JIS-type Japanese keyboards, like the PCXAJ-AA and LK411-JJ,
set the
language
console environment variable to 50, as
in the following example:
>>>set language 50
To use ANSI-type Japanese keyboards, like the LK411-AJ, set the
language
console environment variable to 52, as in the following
example:
>>>set language 52
7.4.2 System-Default Keyboard Setting Might Prevent User Login
When a user logs on to a system, the default keyboard setting
must be appropriate for the keys that the user presses when entering characters
in the user name and password fields.
Otherwise, characters that are correct
from the user perspective, given the keyboard being used, might be treated
as invalid.
In this case, the user cannot log on to the system.
This situation
most often arises when a keyboard is being used in one language and the default
keyboard setting is another language.
You can change the default keyboard
setting at the console prompt or, if the required language is not available
at the console level, by editing the
Xserver.conf
file
to change the keymap used by the X server.
See
keyboard(5)
for more detailed
information about changing keyboard settings.