On Wed, Jul 14, 2010 at 3:46 PM, Peter Hutterer
<[email protected]> wrote:
> This is just a warning about a bug I discovered yesterday. Affected versions
> are all xf86-input-wacom versions when running against X server 1.7 or
> later.
>
> Cause:
> if a button is configured to send key events, wcmEmitKeysyms() calls
> XkbGetCoreMap() to look up the keycode for the keysym configured.
> This call allocs and since we're in the signal handler an allocation may
> hang the system.
>
> Solution:
> We need to buffer the keysym map outside the event handling code and update
> it whenever it updates (that's the tricky bit, mind you).

Are you going to make a patch for it?

> Workaround:
> Don't use keystrokes for buttons if you experience that problem. Normal
> button function will work, it's just the key mapping that triggers this
> problem.

This is not a workaround for those who can not live without
keystrokes. Any other tricks?

Ping

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to