[PATCH] dix: die if we can't activate or init the VCP/VCK.

[Aaron Plattner]

On Tue, Feb 03, 2009 at 04:30:45PM -0800, Peter Hutterer wrote:
> If we have a busted xkb setup, the XKB initialization on the core devices
> fails and leaves us with dev->key->xkbInfo == NULL. This in turn causes
> segfaults lateron.
> 
> Return BadValue when the XKB configuration for a master device failed, and if
> that happens for the VCP/VCK, die semi-gracefully.
> 
> Reported by Aaron Plattner.
> 
> Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>

Looks good to me:

    (EE) XKB: Couldn't open rules file /X/share/X11/xkb/rules/evdev
    XKB: Failed to compile keymap
    Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.

    Fatal server error:
    Failed to activate core devices.

Signed-off-by: Aaron Plattner <aplattner at nvidia.com>

[resending with fixed To: header]