desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #125474
[Bug 1466442] Re: X11 breaks event order under async process_key_event when client applications spent time during XNextEvent
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 <happyaron@xxxxxxxxxx> Sun, 21 Jun 2015 05:53:19 +0800
** Changed in: ibus (Ubuntu)
Status: Fix Committed => Fix Released
--
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 ibus package in Ubuntu:
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
References