X11 breaks event order under async process_key_event when client applications spent time during XNextEvent
Bug #1466442 reported by
Margarita Manterola
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Chromium |
Unknown
|
Unknown
|
|||
ibus |
Unknown
|
Unknown
|
|||
trusty-backports |
Invalid
|
Undecided
|
Unassigned | ||
ibus (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
New
|
Undecided
|
Unassigned | ||
Utopic |
Won't Fix
|
Undecided
|
Unassigned | ||
Vivid |
New
|
Undecided
|
Unassigned | ||
Wily |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This bug comes from: https:/
It affectes Chrome and Chromium making them receive keystrokes out of order if the machine is running slow. (https:/
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+).
Related branches
Changed in ibus (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in trusty-backports: | |
status: | New → Invalid |
Changed in ibus (Ubuntu Utopic): | |
status: | New → Won't Fix |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.