On Wed, Feb 25, 2015 at 11:49:19AM +0100, Olivier Fourdan wrote:
> If the device is present but disabled, the server will still call into
> SetProperty. We don't have a libinput device to back it up in this case,
> causing a null-pointer dereference.
>
> This is a bug specific to this driver that
If the device is present but disabled, the server will still call into
SetProperty. We don't have a libinput device to back it up in this case,
causing a null-pointer dereference.
This is a bug specific to this driver that cannot easily be fixed. All
other drivers can handle property changes even
