X11 breaks event order under async process_key_event when client applications spent time during XNextEvent

[Margarita Manterola]

This bug comes from: https://code.google.com/p/ibus/issues/detail?id=1697 which is fixed by https://github.com/ibus/ibus/commit/b58351ec2f7c057dcfe0aff883064039702a56d7

It affectes Chrome and Chromium making them receive keystrokes out of order if the machine is running slow. (https://code.google.com/p/chromium/issues/detail?id=410649)

The fix applied upstream is to set sync mode to true instead of false by default.

The Chromium bug includes quite a bunch of people affected by this problem. It would be nice if this fix could be applied in affected Ubuntu releases (trusty+).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ibus - 1.5.10-1ubuntu1

---------------
ibus (1.5.10-1ubuntu1) wily; urgency=medium

  * Merge with Debian, remaining changes:
    - ubuntu-no-notification.patch: Don't show the notification if not
      actually upgrading from a previous version.
    - ubuntu-disable-trigger.patch: Disable input method switching under
      Unity; it's handled by gnome-settings-daemon.
    - ubuntu-forward-panel-properties.patch:
      Augment the panel service D-Bus interface so that external consumers
      can detect when the panel service properties are changed.
    - Switch gnome-icon-theme to adwaita-icon-theme
  * ubuntu-title-update.patch:
    - Only update IBus Preferences information for Unity desktop (LP: #1133101)
  * 0001-Set-sync-process_key_event-in-ibus-x11.patch:
    - cherry-pick upstream patch to set sync process_key_event in ibus-x11,
      avoiding the possible misorder of X11 event when async method is used
      (LP: #1466442)

 -- Aron Xu <email address hidden> Sun, 21 Jun 2015 05:53:19 +0800

[David Barnett (mu-mind)]

Looks like the ibus package has been updated in Wily now. Added "trusty-backports" as affected per the comment "It would be nice if this fix could be applied in affected Ubuntu releases (trusty+)".

[David Barnett (mu-mind)]

Is anything blocking the backports?

[David Barnett (mu-mind)]

Why "Won't Fix"?