The biggest reasons seem to be stability and performance utilizing some features of OpenGL. It’s about time someone takes the big leap and wrangles the X monster. If you were to start from scratch right now, designing GNOME, KDE, XFCE, etc., all without Xorg’s quirks and limitations, would it come out the same? I don’t think so.

It’s hard to believe X has been around since 1985. Most people expect all applications to use X, and modern Linux operating systems seem to be reimplementing all kinds of applications to incorporate graphical interfaces. The combination of layers available when developing an application that uses X is staggering.

If you need to forward X the old school unencrypted way, you need to add one line to gdm’s custom.conf file and restart the desktop. Without this, the old “xhost +” won’t do a thing because the out of the box Xorg configuration includes the nolisten tcp flag.

ATI allows xorg.conf to have the normal customized settings you’re used to for X, but it relies on this little PCS database at /etc/ati/amdpcsdb for driver configuration. If you have a customized amdpcsdb, or a binary installation from your favorite package manager is screwing up your X when using the fglrx driver, try reverting back to the default ATI settings.

I have a build machine that runs a build script every day, but it runs on a headless server. That’s not really a problem except that I get a lot of GTK warnings because there’s no display. To get around having these useless warnings in my build log, I start a vnc server so i’ll have a display available on this machine.

How to install Qingy on Fedora. This will work on Fedora 8, Fedora 9, or Fedora 10. It’s all the same, so this will apply to all Fedora versions with directfb and directfb-devel in the repository. If you don’t find them in the repos, just build them from source too.