Sorry, accidentally truncated log output.
Ben Gamari <bgamari.f...@gmail.com> writes:
> Peter Hutterer <peter.hutte...@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,
[ 332.037] (II) Printing all currently active device grabs:
[ 332.037] Active grab 0x41600fc6 (core) on device 'Virtual core pointer'
(2):
[ 332.037] client pid 3674 /home/ben/.xmonad/xmonad-x86_64-linux
[ 332.037] at 322910 (from passive grab) (device thawed, state 1)
[ 332.037] core event mask 0x4
[ 332.037] passive grab type 4, detail 0x1, activating key 0
[ 332.037] owner-events false, kb 0 ptr 1, confine 0, cursor 0x0
[ 332.037] (II) End list of active device grabs
I'm not sure what this grab is intended to do.
Cheers,
- Ben
pgpiuycYGsMmr.pgp
Description: PGP signature
_______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
