1XSERVER(1) General Commands Manual XSERVER(1)
2
6 Xserver - X Window System display server
7
9 X [option ...]
10
12 X is the generic name for the X Window System display server. It is
13 frequently a link or a copy of the appropriate server binary for driv‐
14 ing the most frequently used server on a given machine.
15
17 The X server is usually started from the X Display Manager program
18 xdm(1) or a similar display manager program. This utility is run from
19 the system boot files and takes care of keeping the server running,
20 prompting for usernames and passwords, and starting up the user ses‐
21 sions.
22 Installations that run more than one window system may need to use the
24 xinit(1) utility instead of a display manager. However, xinit is to be
25 considered a tool for building startup scripts and is not intended for
26 use by end users. Site administrators are strongly urged to use a dis‐
27 play manager, or build other interfaces for novice users.
28 The X server may also be started directly by the user, though this
30 method is usually reserved for testing and is not recommended for nor‐
31 mal operation. On some platforms, the user must have special permis‐
32 sion to start the X server, often because access to certain devices
33 (e.g. /dev/mouse) is restricted.
34 When the X server starts up, it typically takes over the display. If
36 you are running on a workstation whose console is the display, you may
37 not be able to log into the console while the server is running.
38
40 Many X servers have device-specific command line options. See the man‐
41 ual pages for the individual servers for more details; a list of
42 server-specific manual pages is provided in the SEE ALSO section below.
43 All of the X servers accept the command line options described below.
45 Some X servers may have alternative ways of providing the parameters
46 described here, but the values provided via the command line options
47 should override values specified via other mechanisms.
48 :displaynumber
50 The X server runs as the given displaynumber, which by default
51 is 0. If multiple X servers are to run simultaneously on a
52 host, each must have a unique display number. See the DISPLAY
53 NAMES section of the X(7) manual page to learn how to specify
54 which display number clients should try to use.
55 -a number
57 sets pointer acceleration (i.e. the ratio of how much is
58 reported to how much the user actually moved the pointer).
59 -ac disables host-based access control mechanisms. Enables access
61 by any host, and permits any host to modify the access control
62 list. Use with extreme caution. This option exists primarily
63 for running test suites remotely.
64 -audit level
66 sets the audit trail level. The default level is 1, meaning
67 only connection rejections are reported. Level 2 additionally
68 reports all successful connections and disconnects. Level 4
69 enables messages from the SECURITY extension, if present,
70 including generation and revocation of authorizations and vio‐
71 lations of the security policy. Level 0 turns off the audit
72 trail. Audit lines are sent as standard error output.
73 -auth authorization-file
75 specifies a file which contains a collection of authorization
76 records used to authenticate access. See also the xdm(1) and
77 Xsecurity(7) manual pages.
78 -bs disables backing store support on all screens.
80 -br sets the default root window to solid black instead of the
82 standard root weave pattern.
83 -c turns off key-click.
85 c volume
87 sets key-click volume (allowable range: 0-100).
88 -cc class
90 sets the visual class for the root window of color screens.
91 The class numbers are as specified in the X protocol. Not
92 obeyed by all servers.
93 -co filename
95 sets name of RGB color database. The default is
96 /usr/share/X11/rgb.
97 -core causes the server to generate a core dump on fatal errors.
99 -deferglyphs whichfonts
101 specifies the types of fonts for which the server should
102 attempt to use deferred glyph loading. whichfonts can be all
103 (all fonts), none (no fonts), or 16 (16 bit fonts only).
104 -dpi resolution
106 sets the resolution for all screens, in dots per inch. To be
107 used when the server cannot determine the screen size(s) from
108 the hardware.
109 dpms enables DPMS (display power management services), where sup‐
111 ported. The default state is platform and configuration spe‐
112 cific.
113 -dpms disables DPMS (display power management services). The default
115 state is platform and configuration specific.
116 -extensionextensionName
118 disables named extension. If an unknown extension name is
119 specified, a list of accepted extension names is printed.
120 +extensionextensionName
122 enables named extension. If an unknown extension name is
123 specified, a list of accepted extension names is printed.
124 -f volume
126 sets feep (bell) volume (allowable range: 0-100).
127 -fc cursorFont
129 sets default cursor font.
130 -fn font
132 sets the default font.
133 -fp fontPath
135 sets the search path for fonts. This path is a comma separated
136 list of directories which the X server searches for font data‐
137 bases. See the FONTS section of this manual page for more
138 information and the default list.
139 -help prints a usage message.
141 -I causes all remaining command line arguments to be ignored.
143 -maxbigreqsize size
145 sets the maximum big request to size MB.
146 -nolisten trans-type
148 disables a transport type. For example, TCP/IP connections can
149 be disabled with -nolisten tcp. This option may be issued mul‐
150 tiple times to disable listening to different transport types.
151 -noreset
153 prevents a server reset when the last client connection is
154 closed. This overrides a previous -terminate command line
155 option.
156 -p minutes
158 sets screen-saver pattern cycle time in minutes.
159 -pn permits the server to continue running if it fails to establish
161 all of its well-known sockets (connection points for clients),
162 but establishes at least one. This option is set by default.
163 -nopn causes the server to exit if it fails to establish all of its
165 well-known sockets (connection points for clients).
166 -r turns off auto-repeat.
168 r turns on auto-repeat.
170 -s minutes
172 sets screen-saver timeout time in minutes.
173 -su disables save under support on all screens.
175 -t number
177 sets pointer acceleration threshold in pixels (i.e. after how
178 many pixels pointer acceleration should take effect).
179 -terminate
181 causes the server to terminate at server reset, instead of con‐
182 tinuing to run. This overrides a previous -noreset command
183 line option.
184 -to seconds
186 sets default connection timeout in seconds.
187 -tst disables all testing extensions (e.g., XTEST, XTrap, XTestEx‐
189 tension1, RECORD).
190 ttyxx ignored, for servers started the ancient way (from init).
192 v sets video-off screen-saver preference.
194 -v sets video-on screen-saver preference.
196 -wm forces the default backing-store of all windows to be When‐
198 Mapped. This is a backdoor way of getting backing-store to
199 apply to all windows. Although all mapped windows will have
200 backing store, the backing store attribute value reported by
201 the server for a window will be the last value established by a
202 client. If it has never been set by a client, the server will
203 report the default value, NotUseful. This behavior is required
204 by the X protocol, which allows the server to exceed the
205 client's backing store expectations but does not provide a way
206 to tell the client that it is doing so.
207 -wr sets the default root window to solid white instead of the
209 standard root weave pattern.
210 -x extension
212 loads the specified extension at init. This is a no-op for
213 most implementations.
214 [+-]xinerama
216 enables(+) or disables(-) the XINERAMA extension. The default
217 state is platform and configuration specific.
218
220 Some X servers accept the following options:
221 -ld kilobytes
223 sets the data space limit of the server to the specified number
224 of kilobytes. A value of zero makes the data size as large as
225 possible. The default value of -1 leaves the data space limit
226 unchanged.
227 -lf files
229 sets the number-of-open-files limit of the server to the speci‐
230 fied number. A value of zero makes the limit as large as pos‐
231 sible. The default value of -1 leaves the limit unchanged.
232 -ls kilobytes
234 sets the stack space limit of the server to the specified num‐
235 ber of kilobytes. A value of zero makes the stack size as
236 large as possible. The default value of -1 leaves the stack
237 space limit unchanged.
238 -logo turns on the X Window System logo display in the screen-saver.
240 There is currently no way to change this from a client.
241 nologo turns off the X Window System logo display in the screen-saver.
243 There is currently no way to change this from a client.
244 -render default|mono|gray|color sets the color allocation policy that
246 will be used by the render extension.
247 default selects the default policy defined for the display
249 depth of the X server.
250 mono don't use any color cell.
252 gray use a gray map of 13 color cells for the X render
254 extension.
255 color use a color cube of at most 4*4*4 colors (that is 64
257 color cells).
258 -dumbSched
260 disables smart scheduling on platforms that support the smart
261 scheduler.
262 -schedInterval interval
264 sets the smart scheduler's scheduling interval to interval mil‐
265 liseconds.
266
268 X servers that support XDMCP have the following options. See the X
269 Display Manager Control Protocol specification for more information.
270 -query hostname
272 enables XDMCP and sends Query packets to the specified host‐
273 name.
274 -broadcast
276 enable XDMCP and broadcasts BroadcastQuery packets to the net‐
277 work. The first responding display manager will be chosen for
278 the session.
279 -multicast [address [hop count]]
281 Enable XDMCP and multicast BroadcastQuery packets to the net‐
282 work. The first responding display manager is chosen for the
283 session. If an address is specified, the multicast is sent to
284 that address. If no address is specified, the multicast is
285 sent to the default XDMCP IPv6 multicast group. If a hop count
286 is specified, it is used as the maximum hop count for the mul‐
287 ticast. If no hop count is specified, the multicast is set to
288 a maximum of 1 hop, to prevent the multicast from being routed
289 beyond the local network.
290 -indirect hostname
292 enables XDMCP and send IndirectQuery packets to the specified
293 hostname.
294 -port port-number
296 uses the specified port-number for XDMCP packets, instead of
297 the default. This option must be specified before any -query,
298 -broadcast, -multicast, or -indirect options.
299 -from local-address
301 specifies the local address to connect from (useful if the con‐
302 necting host has multiple network interfaces). The local-
303 address may be expressed in any form acceptable to the host
304 platform's gethostbyname(3) implementation.
305 -once causes the server to terminate (rather than reset) when the
307 XDMCP session ends.
308 -class display-class
310 XDMCP has an additional display qualifier used in resource
311 lookup for display-specific options. This option sets that
312 value, by default it is "MIT-Unspecified" (not a very useful
313 value).
314 -cookie xdm-auth-bits
316 When testing XDM-AUTHENTICATION-1, a private key is shared
317 between the server and the manager. This option sets the value
318 of that private data (not that it is very private, being on the
319 command line!).
320 -displayID display-id
322 Yet another XDMCP specific value, this one allows the display
323 manager to identify each display so that it can locate the
324 shared key.
325
327 X servers that support the XKEYBOARD (a.k.a. "XKB") extension accept
328 the following options. All layout files specified on the command line
329 must be located in the XKB base directory or a subdirectory, and speci‐
330 fied as the relative path from the XKB base directory. The default XKB
331 base directory is /usr/lib/X11/xkb.
332 [+-]kb enables(+) or disables(-) the XKEYBOARD extension.
334 [+-]accessx [ timeout [ timeout_mask [ feedback [ options_mask ] ] ] ]
336 enables(+) or disables(-) AccessX key sequences.
337 -xkbdir directory
339 base directory for keyboard layout files. This option is not
340 available for setuid X servers (i.e., when the X server's real
341 and effective uids are different).
342 -ardelay milliseconds
344 sets the autorepeat delay (length of time in milliseconds that
345 a key must be depressed before autorepeat starts).
346 -arinterval milliseconds
348 sets the autorepeat interval (length of time in milliseconds
349 that should elapse between autorepeat-generated keystrokes).
350 -xkbmap filename
352 loads keyboard description in filename on server startup.
353
355 X servers that support the SECURITY extension accept the following
356 option:
357 -sp filename
359 causes the server to attempt to read and interpret filename as
360 a security policy file with the format described below. The
361 file is read at server startup and reread at each server reset.
362 The syntax of the security policy file is as follows. Notation: "*"
364 means zero or more occurrences of the preceding element, and "+" means
365 one or more occurrences. To interpret <foo/bar>, ignore the text after
366 the /; it is used to distinguish between instances of <foo> in the next
367 section.
368 <policy file> ::= <version line> <other line>*
370 <version line> ::= <string/v> '\n'
372 <other line > ::= <comment> | <access rule> | <site policy> | <blank line>
374 <comment> ::= # <not newline>* '\n'
376 <blank line> ::= <space> '\n'
378 <site policy> ::= sitepolicy <string/sp> '\n'
380 <access rule> ::= property <property/ar> <window> <perms> '\n'
382 <property> ::= <string>
384 <window> ::= any | root | <required property>
386 <required property> ::= <property/rp> | <property with value>
388 <property with value> ::= <property/rpv> = <string/rv>
390 <perms> ::= [ <operation> | <action> | <space> ]*
392 <operation> ::= r | w | d
394 <action> ::= a | i | e
396 <string> ::= <dbl quoted string> | <single quoted string> | <unquoted string>
398 <dbl quoted string> ::= <space> " <not dqoute>* " <space>
400 <single quoted string> ::= <space> ' <not squote>* ' <space>
402 <unquoted string> ::= <space> <not space>+ <space>
404 <space> ::= [ ' ' | '\t' ]*
406 Character sets:
408 <not newline> ::= any character except '\n'
410 <not dqoute> ::= any character except "
411 <not squote> ::= any character except '
412 <not space> ::= any character except those in <space>
413 The semantics associated with the above syntax are as follows.
415 <version line>, the first line in the file, specifies the file format
417 version. If the server does not recognize the version <string/v>, it
418 ignores the rest of the file. The version string for the file format
419 described here is "version-1" .
420 Once past the <version line>, lines that do not match the above syntax
422 are ignored.
423 <comment> lines are ignored.
425 <sitepolicy> lines are currently ignored. They are intended to specify
427 the site policies used by the XC-QUERY-SECURITY-1 authorization method.
428 <access rule> lines specify how the server should react to untrusted
430 client requests that affect the X Window property named <property/ar>.
431 The rest of this section describes the interpretation of an <access
432 rule>.
433 For an <access rule> to apply to a given instance of <property/ar>,
435 <property/ar> must be on a window that is in the set of windows speci‐
436 fied by <window>. If <window> is any, the rule applies to <prop‐
437 erty/ar> on any window. If <window> is root, the rule applies to
438 <property/ar> only on root windows.
439 If <window> is <required property>, the following apply. If <required
441 property> is a <property/rp>, the rule applies when the window also has
442 that <property/rp>, regardless of its value. If <required property> is
443 a <property with value>, <property/rpv> must also have the value speci‐
444 fied by <string/rv>. In this case, the property must have type STRING
445 and format 8, and should contain one or more null-terminated strings.
446 If any of the strings match <string/rv>, the rule applies.
447 The definition of string matching is simple case-sensitive string com‐
449 parison with one elaboration: the occurrence of the character '*' in
450 <string/rv> is a wildcard meaning "any string." A <string/rv> can con‐
451 tain multiple wildcards anywhere in the string. For example, "x*"
452 matches strings that begin with x, "*x" matches strings that end with
453 x, "*x*" matches strings containing x, and "x*y*" matches strings that
454 start with x and subsequently contain y.
455 There may be multiple <access rule> lines for a given <property/ar>.
457 The rules are tested in the order that they appear in the file. The
458 first rule that applies is used.
459 <perms> specify operations that untrusted clients may attempt, and the
461 actions that the server should take in response to those operations.
462 <operation> can be r (read), w (write), or d (delete). The following
464 table shows how X Protocol property requests map to these operations in
465 The Open Group server implementation.
466 GetProperty r, or r and d if delete = True
468 ChangeProperty w
469 RotateProperties r and w
470 DeleteProperty d
471 ListProperties none, untrusted clients can always list all properties
472 <action> can be a (allow), i (ignore), or e (error). Allow means exe‐
474 cute the request as if it had been issued by a trusted client. Ignore
475 means treat the request as a no-op. In the case of GetProperty, ignore
476 means return an empty property value if the property exists, regardless
477 of its actual value. Error means do not execute the request and return
478 a BadAtom error with the atom set to the property name. Error is the
479 default action for all properties, including those not listed in the
480 security policy file.
481 An <action> applies to all <operation>s that follow it, until the next
483 <action> is encountered. Thus, irwad means ignore read and write,
484 allow delete.
485 GetProperty and RotateProperties may do multiple operations (r and d,
487 or r and w). If different actions apply to the operations, the most
488 severe action is applied to the whole request; there is no partial
489 request execution. The severity ordering is: allow < ignore < error.
490 Thus, if the <perms> for a property are ired (ignore read, error
491 delete), and an untrusted client attempts GetProperty on that property
492 with delete = True, an error is returned, but the property value is
493 not. Similarly, if any of the properties in a RotateProperties do not
494 allow both read and write, an error is returned without changing any
495 property values.
496 Here is an example security policy file.
498 version-1
500 # Allow reading of application resources, but not writing.
502 property RESOURCE_MANAGER root ar iw
503 property SCREEN_RESOURCES root ar iw
504 # Ignore attempts to use cut buffers. Giving errors causes apps to crash,
506 # and allowing access may give away too much information.
507 property CUT_BUFFER0 root irw
508 property CUT_BUFFER1 root irw
509 property CUT_BUFFER2 root irw
510 property CUT_BUFFER3 root irw
511 property CUT_BUFFER4 root irw
512 property CUT_BUFFER5 root irw
513 property CUT_BUFFER6 root irw
514 property CUT_BUFFER7 root irw
515 # If you are using Motif, you probably want these.
517 property _MOTIF_DEFAULT_BINDINGS rootar iw
518 property _MOTIF_DRAG_WINDOW root ar iw
519 property _MOTIF_DRAG_TARGETS any ar iw
520 property _MOTIF_DRAG_ATOMS any ar iw
521 property _MOTIF_DRAG_ATOM_PAIRS any ar iw
522 # The next two rules let xwininfo -tree work when untrusted.
524 property WM_NAME any ar
525 # Allow read of WM_CLASS, but only for windows with WM_NAME.
527 # This might be more restrictive than necessary, but demonstrates
528 # the <required property> facility, and is also an attempt to
529 # say "top level windows only."
530 property WM_CLASS WM_NAME ar
531 # These next three let xlsclients work untrusted. Think carefully
533 # before including these; giving away the client machine name and command
534 # may be exposing too much.
535 property WM_STATE WM_NAME ar
536 property WM_CLIENT_MACHINE WM_NAME ar
537 property WM_COMMAND WM_NAME ar
538 # To let untrusted clients use the standard colormaps created by
540 # xstdcmap, include these lines.
541 property RGB_DEFAULT_MAP root ar
542 property RGB_BEST_MAP root ar
543 property RGB_RED_MAP root ar
544 property RGB_GREEN_MAP root ar
545 property RGB_BLUE_MAP root ar
546 property RGB_GRAY_MAP root ar
547 # To let untrusted clients use the color management database created
549 # by xcmsdb, include these lines.
550 property XDCCC_LINEAR_RGB_CORRECTION rootar
551 property XDCCC_LINEAR_RGB_MATRICES rootar
552 property XDCCC_GRAY_SCREENWHITEPOINT rootar
553 property XDCCC_GRAY_CORRECTION rootar
554 # To let untrusted clients use the overlay visuals that many vendors
556 # support, include this line.
557 property SERVER_OVERLAY_VISUALS rootar
558 # Dumb examples to show other capabilities.
560 # oddball property names and explicit specification of error conditions
562 property "property with spaces" 'property with "'aw er ed
563 # Allow deletion of Woo-Hoo if window also has property OhBoy with value
565 # ending in "son". Reads and writes will cause an error.
566 property Woo-Hoo OhBoy = "*son"ad
567
570 The X server supports client connections via a platform-dependent sub‐
571 set of the following transport types: TCPIP, Unix Domain sockets, DEC‐
572 net, and several varieties of SVR4 local connections. See the DISPLAY
573 NAMES section of the X(7) manual page to learn how to specify which
574 transport type clients should try to use.
575
577 The X server implements a platform-dependent subset of the following
578 authorization protocols: MIT-MAGIC-COOKIE-1, XDM-AUTHORIZATION-1, XDM-
579 AUTHORIZATION-2, SUN-DES-1, and MIT-KERBEROS-5. See the Xsecurity(7)
580 manual page for information on the operation of these protocols.
581 Authorization data required by the above protocols is passed to the
583 server in a private file named with the -auth command line option.
584 Each time the server is about to accept the first connection after a
585 reset (or when the server is starting), it reads this file. If this
586 file contains any authorization records, the local host is not automat‐
587 ically allowed access to the server, and only clients which send one of
588 the authorization records contained in the file in the connection setup
589 information will be allowed access. See the Xau manual page for a
590 description of the binary format of this file. See xauth(1) for main‐
591 tenance of this file, and distribution of its contents to remote hosts.
592 The X server also uses a host-based access control list for deciding
594 whether or not to accept connections from clients on a particular
595 machine. If no other authorization mechanism is being used, this list
596 initially consists of the host on which the server is running as well
597 as any machines listed in the file /etc/Xn.hosts, where n is the dis‐
598 play number of the server. Each line of the file should contain either
599 an Internet hostname (e.g. expo.lcs.mit.edu) or a DECnet hostname in
600 double colon format (e.g. hydra::) or a complete name in the format
601 family:name as described in the xhost(1) manual page. There should be
602 no leading or trailing spaces on any lines. For example:
603 joesworkstation
605 corporate.company.com
606 star::
607 inet:bigcpu
608 local:
609 Users can add or remove hosts from this list and enable or disable
611 access control using the xhost command from the same machine as the
612 server.
613 If the X FireWall Proxy (xfwp) is being used without a sitepolicy,
615 host-based authorization must be turned on for clients to be able to
616 connect to the X server via the xfwp. If xfwp is run without a config‐
617 uration file and thus no sitepolicy is defined, if xfwp is using an X
618 server where xhost + has been run to turn off host-based authorization
619 checks, when a client tries to connect to this X server via xfwp, the X
620 server will deny the connection. See xfwp(1) for more information
621 about this proxy.
622 The X protocol intrinsically does not have any notion of window opera‐
624 tion permissions or place any restrictions on what a client can do; if
625 a program can connect to a display, it has full run of the screen. X
626 servers that support the SECURITY extension fare better because clients
627 can be designated untrusted via the authorization they use to connect;
628 see the xauth(1) manual page for details. Restrictions are imposed on
629 untrusted clients that curtail the mischief they can do. See the SECU‐
630 RITY extension specification for a complete list of these restrictions.
631 Sites that have better authentication and authorization systems might
633 wish to make use of the hooks in the libraries and the server to pro‐
634 vide additional security models.
635
637 The X server attaches special meaning to the following signals:
638 SIGHUP This signal causes the server to close all existing connec‐
640 tions, free all resources, and restore all defaults. It is
641 sent by the display manager whenever the main user's main
642 application (usually an xterm or window manager) exits to force
643 the server to clean up and prepare for the next user.
644 SIGTERM This signal causes the server to exit cleanly.
646 SIGUSR1 This signal is used quite differently from either of the above.
648 When the server starts, it checks to see if it has inherited
649 SIGUSR1 as SIG_IGN instead of the usual SIG_DFL. In this case,
650 the server sends a SIGUSR1 to its parent process after it has
651 set up the various connection schemes. Xdm uses this feature
652 to recognize when connecting to the server is possible.
653
655 The X server can obtain fonts from directories and/or from font
656 servers. The list of directories and font servers the X server uses
657 when trying to open a font is controlled by the font path.
658 The default font path is unix/:7100, catalogue:/etc/X11/fontpath.d,
660 built-ins .
661 The font path can be set with the -fp option or by xset(1) after the
663 server has started.
664
666 /etc/Xn.hosts Initial access control list for display
667 number n
668 /usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/75dpi,/usr/lib/X11/fonts/100dpi
670 Bitmap font directories
671 /usr/lib/X11/fonts/TTF,/usr/lib/X11/fonts/Type1
673 Outline font directories
674 /usr/share/X11/rgb.txt Color database
676 /tmp/.X11-unix/Xn Unix domain socket for display number n
678 /tmp/rcXn Kerberos 5 replay cache for display num‐
680 ber n
681 /usr/adm/Xnmsgs Error log file for display number n if
683 run from init(8)
684 /usr/lib/X11/xdm/xdm-errors Default error log file if the server is
686 run from xdm(1)
687
689 General information: X(7)
690 Protocols: X Window System Protocol, The X Font Service Protocol, X
692 Display Manager Control Protocol
693 Fonts: bdftopcf(1), mkfontdir(1), mkfontscale(1), xfs(1), xlsfonts(1),
695 xfontsel(1), xfd(1), X Logical Font Description Conventions
696 Security: Xsecurity(7), xauth(1), Xau(1), xdm(1), xhost(1), xfwp(1),
698 Security Extension Specification
699 Starting the server: xdm(1), xinit(1)
701 Controlling the server once started: xset(1), xsetroot(1), xhost(1)
703 Server-specific man pages: Xorg(1), Xdmx(1), Xnest(1), Xvfb(1), XDar‐
705 win(1), XWin(1).
706 Server internal documentation: Definition of the Porting Layer for the
708 X v11 Sample Server
709
711 The sample server was originally written by Susan Angebranndt, Raymond
712 Drewry, Philip Karlton, and Todd Newman, from Digital Equipment Corpo‐
713 ration, with support from a large cast. It has since been extensively
714 rewritten by Keith Packard and Bob Scheifler, from MIT. Dave Wiggins
715 took over post-R5 and made substantial improvements.
716X Version 11 xorg-server 1.3.0.0 XSERVER(1)