Add more checks and fix some callers to make sure that the server
core always has a valid screen layout configured.

Do a proper cleanup when one of the termination timeouts trigger
rather than just exiting on the spot. This makes sure we don't leave
stray stuff around, e.g. unix socket files.

We might have an offset in the area of the screen we're tracking,
so make sure that offset is included in the changes we report.

We might only be using part of the X server's screen, so make sure
the layout we calculate is contained within this part.

This makes VNCServer a sufficiently complete interface that callers
don't need to know about the specific implementation (VNCServerST
currently). And assuming that all servers will use sockets is not
that outrageous.

Removed the last parts of VNCSConnectionST's back door in to
VNCServerST and let the parent class fully handle coordination of
clients, and access to the desktop.

Make things simpler by making this a part of the SDesktop interface
that always needs to be implemented.

We cannot assume endian-ness for the cursor we get from XFixes.
Adjust the algorithm to properly follow the specification.

There are some cases where the server state will not automatically
be updated on a change. A prominent one is when only RFB attributes
were changes (e.g. the screen ID) but nothing else. In that case
there is no actual change in the X server, so it never sends any
notification about change back to us.

x0vncserver might only be observing part of the display, so we need
to adjust any coordinates before we give them to the RFB core.

Change Xserver screen through libXrandr. For complex configurations,
all outputs must have corresponding size modes. As a special case, if
the client requests a single screen with an odd size (for example when
adjusting the size of a non-fullscreen vncviewer), find a smaller
suitable mode, and reduce the framebuffer size as well.

It wasn't properly updated in 3112f50 when it was split off from
x0vncserver.cxx.

In XDesktop::start() we allocate pixel buffer and set it as the backend to the given VNCServer.
In XDesktop::stop() we deallocate the buffer, so we must unset it from the VNCServer as well.
Otherwise the VNCServer could try to access it and crash, for example in deferred update.

Legacy systems.

XFixes only reports cursor changes. We must manually call
XFixesGetCursorImage() when starting.

Define ledNames in XDesktop.cxx, rename N_LEDS to XDESKTOP_N_LEDS