[BUG] Touchscreen woes
bgamari.foss at gmail.com
Fri Nov 29 09:20:54 PST 2013
Ben Gamari <bgamari.foss at gmail.com> writes:
> Peter Hutterer <peter.hutterer at who-t.net> writes:
>> you need to check again here. each event is processed twice, once for the
>> device and once for the master. you need to make sure that kbd->name ==
>> "Virtual core keyboard", you can ignore the actual device for most purposes.
>> the actual device has PointerRootWin, usually, the VCK has the actual focus.
> It seems that when keyboard input is in its paused state only the
> device events are delivered. The core keyboard events are only
> delivered after another mouse event has occurred. The backtrace while
> the old keyboard events are being processed looks like,
Apparently the grab causing this pause is held by xmonad,
(II) Printing all currently active device grabs:
Active grab 0x41800ff7 (core) on device 'Virtual core:
client pid 2835 /home/ben/.xmonad/xmonad-x86_64-linux
at 1751744 (from passive grab) (device thawed, state
core event mask 0x4
passive grab type 4, detail 0x1, activating key 0
owner-events false, kb 0 ptr 1, confine 0, cursor 0x0
(II) End list of active device grabs
I'm not sure what this grab is intended to do.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 489 bytes
Desc: not available
More information about the xorg