XInput device properties ; keymaps service & console switch

[Peter Hutterer]

On Sat, Aug 21, 2010 at 07:31:21AM -0700, Sebastian Glita wrote:
> Hi,
> 
> When using CTRL+ALT+F1..12 to switch between consoles and Xorg, it happens that:
> 
> 1.
> 
> When I do like this:
> 
>     user at localhost ~ $ xinput set-int-prop 'ImPS/2 Generic Wheel Mouse' 'Device 
> Enabled' 8 0
>     user at localhost ~ $ xinput list-props 'ImPS/2 Generic Wheel Mouse'
>     Device 'ImPS/2 Generic Wheel Mouse':
>             Device Enabled (131):   0
>  
> and then switch to console (CTRL+ALT+F1) and then back again, I get this:
> 
>     user at localhost ~ $ xinput list-props 'ImPS/2 Generic Wheel Mouse'
>     Device 'ImPS/2 Generic Wheel Mouse':
>             Device Enabled (131):   1
> 
> So the properties' values change betwen console switching.

VT switching disables all devices and re-enables them when coming back. It's
been like this for ages and I'm not really inclined to change this
behaviour at this point.

Generally, any use of xinput is a once-off effect only and the setting set
by xinput is not guaranteed to be maintained and/or monitored for changes.

> 2.
> 
> When I restart keymaps service like this:
> 
>     user at localhost ~ $ #eselect rc restart keymaps
>     user at localhost ~ $ /etc/init.d/keymaps restart
> 
> then whenever I press:
> 
>   - F1..12 keys or
>   - Alt+F1..12 or
>   - the windows key,
> 
> whether Control (CTRL) key is pressed or released, it doesn't matter, I get a 
> console switch each time.

what does xev say about key presses? is the ctrl key stuck?

Cheers,
  Peter