desktop-packages team mailing list archive

[Aron Xu <1466442@xxxxxxxxxxxxxxxxxx>]

** Also affects: ibus (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Also affects: ibus (Ubuntu Wily)
   Importance: Undecided
       Status: Fix Released

** Also affects: ibus (Ubuntu Utopic)
   Importance: Undecided
       Status: New

** Also affects: ibus (Ubuntu Vivid)
   Importance: Undecided
       Status: New

** Changed in: trusty-backports
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1466442

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

Status in Chromium:
  Unknown
Status in IBus:
  Unknown
Status in Trusty Backports:
  Invalid
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Trusty:
  New
Status in ibus source package in Utopic:
  New
Status in ibus source package in Vivid:
  New
Status in ibus source package in Wily:
  Fix Released

Bug description:
  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+).

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium/+bug/1466442/+subscriptions