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 dev
On Tue, Feb 3, 2009 at 4:51 PM, Peter Hutterer wrote:
> On Tue, Feb 03, 2009 at 04:46:05PM -0800, Dan Nicholson wrote:
>> On Tue, Feb 3, 2009 at 4:30 PM, Peter Hutterer
>> wrote:
>> > If we have a busted xkb setup, the XKB initialization on the core devices
>> > fails and leaves us with dev->key
On Wed, Feb 04, 2009 at 10:51:21AM +1000, Peter Hutterer wrote:
> From 29b2848cecf1ccde8fba7d7b1bfafa03873753d8 Mon Sep 17 00:00:00 2001
> From: Peter Hutterer
> Date: Wed, 4 Feb 2009 10:11:13 +1000
> Subject: [PATCH] dix: die if we can't activate or init the VCP/VCK.
>
>
>From 29b2848cecf1ccde8fba7d7b1bfafa03873753d8 Mon Sep 17 00:00:00 2001
From: Peter Hutterer
Date: Wed, 4 Feb 2009 10:11:13 +1000
Subject: [PATCH] dix: die if we can't activate or init the VCP/VCK.
If we have a busted xkb setup, the XKB initialization on the core devices
fails and leave
On Tue, Feb 3, 2009 at 4:30 PM, 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
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.
Rep
