X Window System Release 7.3 2007-09-06 The X11R7.3 release incorporates the 1.4 version of the X.Org X Server, which is most notable for the addition of input hotplugging support, with device detection managed either through HAL or a dbus-connected manager. Also new in the X Server since X11R7.2 is the 1.2 version of the RandR extension, which allows for runtime configuration of outputs within X Screens and an improved static configuration system for multihead in a RandR 1.2 environment. This release also rolls in a new driver, xf86-video-vermilion, and re-adds the xf86-video-glide driver which had been present in the monolithic releases. The xbacklight command-line tool is also added for configuring backlight properties through RandR 1.2. Other modules have also gone through the usual host of updates and bugfixes as well. See http://wiki.x.org/wiki/Releases/7.3 for a list of modules updated in this release. Not all bugs could be fixed in time for this release, and the following known issues are regrettably left in at this time, to be remedied in later point releases of the modules involved: Bug #7248: Multiple PCI domains no longer work on Linux. This has been present since the 1.3 server, at least. It is expected to be fixed on master (to be server 1.5), and a minimal fix may be backported when that happens. Bug #7512: Memory leak with GLX pixmaps. This couldn't get tracked down in time for release. Bug #11796: Two-color cursors misrendered on big-endian systems. The problem was not fully understood at time of release, and the interim fix was not included. Bug #11802: When the appropriate input driver is not found for static configuration, the server may crash. Bug #12055: Server crash with compiz. Reporter didn't have time to follow up. Bug #12145: In traditional (multi-Screen) multihead mode, the cursor may be stuck on one of the heads. This is a bug in evdev which may also exist in other input drivers, and will be fixed in upcoming point releases. Bug #12286: Bug in libwfb, which arrived too late to make it in. bug #12291: Failure in an error path of the new input code may lead to server crashes during server exit. This should have made it in, and was an oversight.