[Fedora-i18n-bugs] [Bug 756595] ibus Ctrl+Space conflicts with Eclipse's Content Assist and various other IDEs/editors

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=756595

--- Comment #57 from fujiwara  ---
(In reply to comment #56)
> sorry, ECOFFEE. that should read XIAllowEvent, defined in XInput.h
> http://cgit.freedesktop.org/xorg/lib/libXi/tree/include/X11/extensions/
> XInput2.h#n447
>
> Works more or less the same way as XAllowEvents.

I'm not sure how XIAllowEvents can be used.
When I call XIAllowEvents (xdisplay, XIAllMasterDevices, SyncKeyboard,
CurrentTime), XI_BadDevice was returned below.

This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 591 error_code 149 request_code 141 minor_code 53)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

RANDR  (opcode: 149, base event: 100, base error: 165)
    XInputExtension  (opcode: 141, base event: 78, base error: 149)