AIX for PS/2 X Windows User's Guide
AIX X-Windows User's Guide
Appendix B. X-Windows Messages
B.0 Appendix B. X-Windows
Messages
B.1 Messages Created by the
aixwm Command
B.2 Messages Created by the
keycomp Command
B.3 Messages Created by the
X Command
B.4 Messages Created by the
aixterm Command
B.5 Messages Created by the
xclock Command
B.6 Messages Created by the
xhost Command
B.7 Messages Created by the
xinit Command
B.8 Messages Created by the
xopen Command
B.0 Appendix B. X-Windows
Messages
This appendix contains error messages that are generated
by the X-Windows licensed program. When X-Windows creates a message,
it will display the message in one of the following ways:
at the current virtual terminal
at the console
in a message pop-up in the window that had
the error. To remove the
message pop-up, click any button
on your mouse within the pop-up.
Read the message and take the appropriate action.
X-Windows messages start with the number 073.
Refer to IBM RT Messages Reference for information on
other messages.
B.1 Messages Created by
the aixwm Command
073-001 The aixwm command cannot open menu
font font.
Cause: You specified a font that does not exist. The
aixwm -fn flag
specifies a font to
use in the display of the menu. The default
font is Rom14.500 for
a large display and Rom10.500 for a small
display.
Action: Indicate a valid font for the aixwm -fn flag and try again.
Refer to "aixwm" in
topic 2.6 for more information.
073-002 The aixwm command cannot open size
font font.
Cause: You specified a font that does not exist. The
aixwm -fs flag
specifies a font to
use when sizing a window. The default font is
Rom14.500 for a large
display and Rom10.500 for a small display.
Action: Indicate a valid font for the aixwm -fs flag and
try again.
Refer to "aixwm"
in topic 2.6 for more information.
073-003 The aixwm command cannot open icon
font font.
Cause: You specified an icon font that does not exist.
The aixwm -fi
flag specifies a font
to use when hiding a window. The default
font is Rom14.500 for
a large display and Rom10.500 for a small
display.
Action: Indicate a valid font for the aixwm -fi flag and
try again.
Refer to "aixwm"
in topic 2.6 for more information.
073-005 The aixwm command cannot open menu
text file filename.
Cause: You requested a file that cannot be opened.
Action: Make sure you have permission to access this file.
Then, try
again. Refer
to "aixwm" in topic 2.6 for more information.
073-006 The aixwm command cannot find a valid
entry in menu text file
filename.
Cause: You requested an entry in a menu text file that was
not valid.
Action: Make sure that you requested the proper file and
that the file
contains valid
text entries. Use an editor to convert the text
entries in the
menu text file. Or, re-install X-Windows. Refer
to "aixwm" in
topic 2.6 for more information.
073-007 The aixwm command cannot find file
filename.
Cause: You requested a menu text file that does not exist.
Action: Make sure that you requested the proper file or that
it exists.
Then, try again.
Refer to "aixwm" in topic 2.6 for more
information.
073-008 The aixwm command cannot find menu
text file filename. This file
must be in your $HOME directory or /usr/lpp/X11/defaults.
Cause: You requested a menu text file that does not exist.
Action: Check the following:
That the file exists in $HOME
or in /usr/lpp/X11/defaults
That the filename is correct.
Then, try again. Refer to "aixwm" in topic 2.6
for more information.
073-009 A text entry line number in filename
is not valid.
Cause: You requested a text entry that is either not valid
or not in the
menu text file.
Action: Verify that the format of the entry in line number
that you
requested is the
same as the #nnn in the file. Then, try again.
073-010 The function name function is not
valid in Xset.txt file.
Cause: You requested a function that is not valid in the
Xset.txt file.
Action: Make sure the function name is correct. Then,
try again.
073-011 Warning: The foreground color
color is the same as the background
color.
Cause: You specified a foreground color that is the same
as the
background color on
your display.
Action: Specify another foreground color. For more
information, see
"Color Specification"
in topic 2.3.4.
073-012 Warning: The background color
color is the same as the foreground
color.
Cause: You specified a background color that is the same
as the
foreground color on
your display.
Action: Specify another background color. See "Color
Specification" in
topic 2.3.4 for
more information.
073-013 The aixwm command cannot open output
print file filename.
Cause: You do not have write permission to the file on \tmp.
Action: Make sure you have permission to access this file.
Then, try
again.
073-014 When the client program opened a
window, it specified an invalid
initial_state flag.
Cause: Your client program requested an invalid initial_state
flag in the
XWMHints structure.
Action: Change the initial_state field in the XWMHints structure
to one
of the following:
DontCareState
NormalState
ClientIconState
IconicState
InactiveState
IgnoreState
Relink the client program and try again. For
more information on
XWMHints, refer to the IBM AIX X-Windows Programmer's
Reference.
073-015 The aixwm command cannot create a
title for window window name.
Cause: You requested a title bar for an InputOnly window.
X-Windows does
not support title bars
for InputOnly windows.
Action: Change the window class of this window to InputOutput
and try
your request again.
Or, use a NULL window name and try again.
For more information about InputOnly and InputOutput
windows, refer to the IBM AIX X-Windows Programmer's Reference.
073-016 The client program passed an invalid
pixmap ID for the icon
pixmap.
Cause: Your client program passed a pixmap ID for the icon
pixmap that is
not valid.
Action: Set the pixmap ID to a valid ID and try again.
Or, set the
pixmap ID to NULL and
try again.
For more information about pixmaps, refer to the IBM
AIX X-Windows
Programmer's Reference.
073-017 The aixwm command cannot make a connection
to the X Server.
Cause: Your request to connect to the X Server failed because
the server
is not running.
Action: Make sure that the X Server is running. If
the X Server is not
running, execute
xinit and try again. If the X Server is
running, make
sure that the display number you are using is a
valid display
number and try again.
073-018 The aixwm command cannot store the
wmCursor in StoreCursors.
Cause: The aixwm cannot find the specified cursor font.
Specify a valid
cursor font using the
aixwm - fc option.
Action: Check that cursor glyphs exists in your cursor font.
Otherwise,
follow your local
procedures for reporting software problems.
073-019 The aixwm command cannot query the
string width in SetUpWindow.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-020 The aixwm command cannot open the
menu in SetUpWindow.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-021 The aixwm command cannot open the
menu button in SetUpWindow.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-022 The aixwm command cannot create size
Window in SetUpSizeWindow.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-023 The aixwm command cannot allocate
memory.
Cause: There is insufficient system memory for aixwm.
Action: Increase the physical system memory or terminate
unnecessary
processes, and
try aixwm again.
073-024 The aixwm command cannot install
the default colormap.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problem.
073-025 The aixwm command cannot open titlebar
font font name.
Cause: The aixwm command cannot open the titlebar font because
the font
information is not valid
or not supported.
Action: Specify a valid titlebar font with the aixwm - ft
flag. Then,
try again.
Refer to "aixwm" in topic 2.6 for more information.
B.2 Messages Created by the
keycomp Command
073-030 The keycomp command cannot fseek
output file.
Cause: Setting the position of next output operation failed.
Action: Be sure that the standard output is redirected into
a file.
073-031 Keycomp parse error at item <#>
on line <#> : <Error description>.
Cause: A syntax error was found at the item and line indicated.
Action: Correct the syntax error in the keycomp source file
and execute
the keycomp command
again.
B.3 Messages Created by the
X Command
073-035 The X Server cannot open the default
font font name.
Cause: You requested a font that either does not exist or
is not
supported.
Action: Make sure that the font or font path is valid.
073-036 The X Server cannot open the default
cursor font font.
Cause: You requested a cursor font that the X Server cannot
access.
Action: Make sure that the font exists or that the default
font path is
valid. Use
the -fn or the -fp flag to change these values when
starting the server.
The -fn flag specifies the text font
for the server.
The -fp flag specifies the path where
the server will look for the
fonts.
Refer to "X" in topic 2.8 for more information about
these flags.
073-037 The X Server cannot open RGB database
filename.
Cause: When invoking the X Server with the X -D flag, you
specified a
database path that is
not valid.
Action: Check the database filename. If the database
is valid, try to
invoke the server
again. For more information about this flag,
refer to "X" in
topic 2.8.
073-038 usage: X [option]
Cause: You attempted to invoke the server with a flag that
is not valid
or with the -help option.
Action: Try again with the correct flags.
073-039 An internal error occurred while
attempting to initialize the
predefined atoms.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-040 An invalid event number was specified
during internal processing.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-041 A NULL cursor was detected during
cursor processing.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-042 An invalid keyboard event was detected
during keyboard processing.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-043 An invalid client ID was detected
during internal processing of
events.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-044 An invalid client ID was detected
during internal processing of
passive grabs.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-045 An internal error was detected during
the initialization of the
server.
Cause: This could be a problem with your program.
Action: Follow your local procedures for reporting software
problems.
073-046 An internal error occurred during
screen initialization.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-047 An invalid client ID was used in
a Resource Manager function.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-048 An invalid function was specified
in a Resource Manager function.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-049 An invalid resource id was specified
in an internal function.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-050 Error number xxx was received while
attempting to bind a UNIX
domain socket.
Cause: The server cannot access the a UNIX domain socket.
Action: Check permissions in /dev/sock file. Refer
to the AIX Operating
System Technical
Reference for more information.
073-051 An error was detected while attempting
to bind the TCP socket.
Cause: The X Server cannot access a TCP/IP socket.
Action: Be sure the network is available, the network is
configured
correctly, and
any necessary devices are configured correctly.
073-052 The Xfree function detected an invalid
memory position while
attempting to free existing storage.
Cause: This could be a software problem.
Action: Follow your local procedures for reporting software
problems.
073-053 The X Server has attempted to add
a line cap to a line segment of
0 length.
Cause: You attempted to draw a line of zero length (a point)
with a cap
style of CapProjecting
and the server cannot determine the
direction to project
the cap.
Action: Select a different cap style. Draw a line of
longer length.
073-055 The X Server is unable to query current
keyboard.
Cause: The X Server cannot detect the current keyboard.
Action: Check that the keyboard is in working condition and
firmly
attached to the
machine.
073-056 The X Server is unable to query display
device IDs.
Cause: The X Server cannot detect the specified display.
Action: Check that the device of the specified type is attached
and
configured correctly.
073-057 The X Server is unable to locate
display number.
Cause: The X Server cannot locate the display specified.
Action: Be sure that the device specified is attached to
the X Server and
is configured
correctly.
073-066 The X Server cannot configure the
locator device.
Cause: The X Server cannot configure the locator device.
Action: Be sure that the device is attached to the computer
and
configured correctly.
B.4 Messages Created by the
aixterm Command
073-070 The aixterm command encountered the
internal error "xxxxx".
Cause: An internal error occurred inside aixterm. This
error is normally
caused by lack of physical
memory when allocating memory for
windows and buffers.
Action: Check for unusually large window sizes or unusually
small
physical memory
with respect to the number of applications
running on the
system. Otherwise, follow your local procedures
for reporting
software or hardware problems.
073-071 The aixterm command cannot allocate
memory.
Cause: There was not enough system memory for the aixterm
window size
requested.
Action: Increase the physical system memory or use a smaller
window size.
073-072 The aixterm command cannot allocate
bitmap bitmap filename.
Cause: You requested a bitmap file that is too large for
the system
memory available.
Action: Use a smaller bitmap file or increase the physical
system memory.
073-073 The aixterm command encountered a
syntax error in bitmap bitmap
filename.
Cause: You cannot read the bitmap file because a syntax error
was found.
Action: Check your file for syntax errors. For an example
of a bitmap
file, refer to
/usr/include/X11/bitmaps.
073-074 The aixterm command found an invalid
font entry at line number.
Cause: You specified an entry in /usr/lpp/X11/defaults/Xfonts
that is
incorrect or not found.
Action: Refer to the IBM AIX X-Windows Programmer's Reference
for
information about
the /usr/lpp/X11/defaults/Xfonts file syntax.
073-075 The aixterm command cannot open the
bitmap bitmap filename.
Cause: You specified a bitmap file that does not exist or
that you do not
have permission to read.
Action: Check that the file exists and that you have permission
to access
it.
073-076 X Server named display name was not
found.
Cause: The aixterm command cannot find the X Server running
on the host
you specified.
Action: Verify that the X Server is running on the host specified.
073-077 The aixterm command cannot execute
command name.
Cause: The command name command after the aixterm -e option
cannot be
executed.
Action: Check the following:
command name exists,
command name is in a directory in the
environment path,
You have permission to execute the command.
For more information, refer to "aixterm" in topic
2.5.
073-078 The aixterm command cannot open font
font name.
Cause: The aixterm command cannot open the font file specified
because it
does not exist in /usr/lpp/fonts
or you do not have permission to
access the file /usr/lpp/fonts.
Action: Verify that the font exists in /usr/lpp/fonts and
that you have
permission to
access it.
073-079 No system ptys are available for
aixterm.
Cause: The aixterm command tried to open a pty device, but
no ptys were
available.
Action: Add more pty devices with the devices command.
(Auto enable and
logger should
be FALSE.)
B.5 Messages Created by the
xclock Command
073-081 The xclock command cannot open the
display display name.
Cause: You requested a connection to the X Server and it
failed.
Action: Verify that the specified X Server (display) is running.
073-082 The xclock command cannot open font
font name.
Cause: The xclock command cannot open the font file specified
because it
does not exist in /usr/lpp/fonts
or, you do not have permission to
access the file /usr/lpp/fonts.
Action: Verify that the font exists in /usr/lpp/fonts
and that you have
permission to
access the file.
B.6 Messages Created by the
xhost Command
073-083 The xhost command cannot open display
display name.
Cause: The xhost command cannot find an X Server running
on the specified
host.
Action: Verify that an X Server is running on the host specified.
073-084 The xhost command cannot get a host
name.
Cause: The xhost command cannot get the host name information
from a name
server program or from
the /etc/hosts file.
Action: Verify that the network is working. If the
name server program
cannot be accessed,
make sure the host name entry exists in the
/etc/hosts file
and try again.
073-085 The host name hostname is unacceptable.
Cause: You specified a host name to the xopen command
that is not
recognized.
Action: Check the host name you specified and try again.
B.7 Messages Created by the
xinit Command
073-086 Unable to start the X Server
Cause: The X Server cannot execute.
Action: For more information check the /tmp/.X?.msgs file,
where ? is the
display (server)
number.
B.8 Messages Created by the
xopen Command
073-087 The xopen command was not invoked
on the local display display
name system.
Cause: The xopen command cannot be invoked from a remote
terminal window
because the new virtual
terminal would be created on the remote
system.
Action: Invoke xopen from a local terminal window.
073-088 The xopen command cannot connect
to display display name.
Cause: The xopen command cannot find an X Server running
on the host
specified.
Action: Verify that an X Server is running on the host specified.
073-089 The xopen command cannot open the
font fontname.
Cause: You cannot open the font file because it does not
exist in
/usr/lpp/fonts
or, you do not have permission to access
/usr/lpp/fonts.
Action: Verify that the font is in /usr/lpp/fonts and that
you have
permission to
access the file.
073-090 The xopen command cannot open the
bitmap file bitmap file.
Cause: You cannot open the bitmap file because it does not
exist or, you
do not have permission
to access it.
Action: Verify that the file exists and that you have permission
to
access it.
073-091 The xopen command encountered a syntax
error in bitmap file
filename.
Cause: You cannot read a bitmap file because a syntax error
was found.
Action: Check the file for syntax errors. For an example
of a bitmap
file, refer to
/usr/include/X11/bitmaps.
9595 Main Page
|