On 2006/04/11, ["Xorg"] version 7.0 was uploaded to unstable. This is a major change in the packaging, and is therefore a complex upgrade which various problems for users. The ["XStrikeForce"] is working through the bugs, but in the meantime this page is here to help users out with the transition. Here are some of the more common problems and how to solve them:

Installing

The meta-package xorg is the new metapackage for X. The previous metapackages x-window-system and x-window-system-core are now transitional packages, both of which only depend on this package, and they will go away following the etch release. It is highly recommended that most users install this package in order to ensure that they have a full functional X system. This can be done with the following command:

aptitude install -t unstable xorg

missing /etc/X11/Xsession (Fixed in x11-common 1:7.0.17)

xfree86-common 7.0.16 moves /etc/X11/Xsession causing a confmiss when x11-common tries to replace it. you can force it to be reinstalled:  apt-get -o DPkg::Options::="--force-confmiss" --reinstall install x11-common 

x11-common installation

The x11-common package is required to be successfully installed before any of the other ?X11R7 packages are installed. The reason for this is that it is responsible for moving directories around so that they're in the new, FHS-compliant, format.

The biggest problem with this is that the /usr/X11R6/bin directory must become a symlink to /usr/bin, where all the Xorg binaries are now stored. Because no one likes to have their programs deleted out from under them, the installation of x11-common will fail if it tries to remove this directory and fails. x11-common currently conflicts with packages in Debian that are known to install anything to /usr/X11R6/bin, so that the directory can be automatically cleared as well as possible before attempting installation. (If you find a package in Debian that installs to /usr/X11R6/bin, but x11-common doesn't conflict with it, please file a bug report against x11-common!) Despite this safety measure, several unofficial packages or programs, (including some versions of opera and fglrx), can install software to this directory. Because x11-common does not conflict with these packages (it would not be feasible to add a conflict against every single unofficial package ever created), its installation will fail.

The workaround for this is that if you have left-over items hanging around /usr/X11R6/bin, simply move them to a temporary location (or even to /usr/bin, where /usr/X11R6/bin will eventually point) until x11-common has successfully installed and made /usr/X11R6/bin in to a symlink. Then simply move them back once x11-common has installed successfully. This will prevent many common errors with the installation, and it provides you with the full knowledge of what's going on with your system. Forcing the installation of x11-common has been shown to cause the expected breakages, so it's highly recommended that you use this workaround instead.

Missing xserver-xorg

Some people have reported that xserver-xorg is removed upon upgrade. While this issue is being worked out, if your X server mysteriously refuses to start, be sure to check to see that this package is actually installed.

Check your /etc/apt/sources.list and make sure you have deb http://ftp.debian.org/debian unstable main contrib listed. The old http://amd64.debian.net/debian-pure64/ repositories are obsolete and is one possible reason that some people are reporting that xserver-xorg is removed on the dist-upgrade. Do *NOT* do the upgrade if xserver-xorg is going to be removed as part of the upgrade or you will not be able to start KDM/X afterwards.

Missing Drivers

(EE) No Input driver matching `$foo'

Now that all the drivers are packaged separately, you may need to install some extra packages. The simplest way to do this is to install the xserver-xorg-video-all and xserver-xorg-input-all packages or the xorg metapackage. Alternately, when you get the above message, look for a package named like xserver-xorg*foo. You will almost definitely need to install:

And you are likely to need to install a xserver-xorg-video-foo driver for your video card.

Font path change

Please Note: If you experience this bug when xserver-xorg-core version 1:1.0.2-5 is installed, report it to the ["XStrikeForce"] with reportbug. Thanks!

(EE) Unable to find default font: fixed

The xfonts-base package now installs fonts to /usr/share/fonts/X11/. You will need to edit your ?FontPath entries in /etc/X11/xorg.conf. /usr/lib/X11/fonts becomes /usr/share/fonts/X11/. Do the same change to all /usr/lib/ entries. $ ls /usr/share/fonts/X11/ to get a list of directories.

Also note that x11-common now conflicts with xfs, so you may want to remove the ?FontPath to unix/:7100.

Another reason X can't find the fixed font is your font.alias file may be missing (it's in your fontpath). It may have gotten removed if your dist-upgrade removes xserver-org. If you do a "man mkfontdir", you'll see what format it has to be in. The X server needs either a font or aliases for "fixed" and "cursor" in order to start up. More help can be found here: [http://xorg.freedesktop.org/wiki/FAQErrorMessages#head-a570197d15005a2c71cbb5e565114e2c04a573a3 Xorg-FAQ]. If you have unknown parametr errors with update-font-dir, you may have that file in /usr/local/sbin and /usr/sbin (the newest is in /usr/sbin); remove the update* files in /usr/local/sbin.

Incorrect paths in xorg.conf

Please refer to /usr/share/doc/xserver-xorg-core/NEWS.Debian.gz. You may need to edit paths in your xorg.conf for fonts (see above), kbd data or modules. Note that the paths for fonts and the modules should not be an issue as of xserver-xorg-core 1:1.0.2-6. If you encounter this issue when this version of the server or greater is installed, please report a bug against the xserver-xorg-core package using reportbug.

Can't Load Modules

Errors about not being able to load modules (most notably glcore) can be fixed by removing the line to load them from your xorg.conf. This can be done automatically for non-customized config files by running dpkg-reconfigure xserver-xorg as root.

kdm

As of version 4:3.5.2-2 kdm shold be working fine. If not, please use reportbug to report an appropriate bug against kdm. As a work-around, if the kdm display manager does not start the X server, make sure that /etc/kde3/kdm/kdmrc contains the line ServerCmd=/usr/bin/Xorg -br instead of ServerCmd=/usr/X11R6/bin/X -br.

gdm

If the gdm display manager does not start the X server, make sure that /etc/gdm/gdm.conf contains the line command=/usr/bin/Xorg -audit 0 instead of command=/usr/X11R6/bin/X -audit 0 in the [server-Standard] section.

Comment: The related files seem to be /usr/share/gdm/defaults.conf and /usr/share/gdm/factory-defaults.conf, not /etc/gdm/gdm.conf.

wdm

wdm is working fine, people may edit /etc/X11/wdm/Xservers to update the server path from /usr/bin/X11/X to /usr/bin/Xorg

nvidia (orig) binary drivers

If installing the original nvidia drivers from the nvidia.com drivers download page with the official driver script, use --x-module-path=/usr/lib/xorg/modules/. Otherwise not only the driver itself will be installed in /usr/X11R6/lib64/modules/drivers or /usr/X11R6/lib/modules/drivers, but also the OpenGL libraries might not work.

You might have problems using an external monitor when using the nvidia binary drivers on a laptop. If so, try adding this line to the Device section in your /etc/X11/xorg.conf:

If using module assistant to install the nvidia drivers try switching to the free driver, nv, while the issues are worked out. You can do this by editing xorg.conf.

ati binary drivers (on amd64)

The ati drivers (as generated by ati's installer pack) seem to suffer from the same problems as the nvidia ones: it still puts its libGL into /usr/X11R6/lib, while all executables use the libGL in /usr/lib. I don't know of an easy fix at the moment, except for some manual hacking in ati's unpacked driver pack.

The driver itself will work (if ?ModulePath "/usr/X11R6/lib/modules" is added to Xorg.conf), but it won't do anything relating to GL.

DRI with i915

libmesa stops working after upgrade to 7.* of XOrg with i915 driver (and maybe some others). Mesa in sid is too old and the i915 driver is too new. It is necessary to download new drivers from http://dri.freedesktop.org/snapshots/ and copy *_dri.so files to /usr/lib/dri/. This is [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=359328 bug# 359328]. The driver will soon be rolled back to the version appropriate for the mesa in sid.

startkde

If 'startkde' refuses to load, copy /usr/lib/X11/xinit/xinitrc to ~/.xinitrc and open it in your favourite text editor; remove anything under the line # start some nice programs and add exec startkde &. Running 'startx' will give you your KDE back.

Missing manpages

There are currently no manpages installed for things like evdev. This is currently being tracked as [http://bugs.debian.org/362489 Bug #362489]

The /usr/X11R6 directory

Since everything under /usr/X11R6 has been moved out, the directory itself is no longer used nor pertinant to the system, save for the problems where a workable solution has been found above. Since X.org is X11R7, X11R6 is phased out and thus the naming convention of the directory goes, too.

Ctrl-Alt-Function keys not working

If Ctrl-Alt-Function keys stop working, try removing the keyboard variant option from xorg.conf if it's there. (option "?XkbVariant") dpkg-reconfigure xserver-xorg and leave the keyboard variant field empty.