Bug 1428504 - Default (wayland) gnome session has erratic keyboard to display response
Summary: Default (wayland) gnome session has erratic keyboard to display response
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-02 17:19 UTC by Joel C Ewing
Modified: 2017-12-12 10:58 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:58:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joel C Ewing 2017-03-02 17:19:33 UTC
If this is not assigned to the appropriate software component, re-route as appropriate, but it seems to be an issue related to gnome desktop and specifically with the default gnome wayland desktop sessions in f25.

Description of problem:
At times I have observed a delay of as long as 0.5 to 1 second before the display changes to reflect keys pressed on the keyboard when speed-typing text.  This has occurred with text windows in multiple applications (Documents with LibreOffice Writer, Emails with Thunderbird, txt documents with gedit), so it doesn't appear to be an application problem.  It only seems to occur under a "gnome" login under f25, not under  a "gnome-on-Xorg" login, and was never observed on f22.  The display seems to keep pace with typing, but a delay is sometimes, but not always, obvious when one realizes an error has been keyed and in attempting to correct it find you have entered the wrong number of backspaces and re-keyed characters in the wrong place because the display is significantly out of sync with what has been keyed.  I find it takes me 3 or 4 tries at progressively slower typing speeds to make a simple correction correctly.  There are times when I have been certain I entered the correct number of backspaces, but have had to wait at least one second before the display finally confirms the last backspace.  It doesn't always do this, but once the problem starts it seems to become more persistent.

Version-Release number of selected component (if applicable):  gnome-session and other gnome packages are at 3.22.2-3


How reproducible:
If you are a reasonably fast touch-typist, key enough text, make enough typos and attempted corrections (more than one less than ten), eventually the problem will surface. After re-booting at one point, I thought the problem had disappeared, but after ten minutes, I saw my first occurrence and then after that it again became more persistent.



Additional info:
In case hardware might be an issue, this was observed on Asus BP6375 desktop, which has Intel Core i5 CPUs and Intel Ivybridge graphics.

It took me a while to discover that the logon panel had an option under the settings gear to use "Gnome on Xorg" instead of the default "Gnome" (wayland) desktop, and longer to convince myself that changing to Gnome on Xorg seemed to circumvent the problem.

I suspect this description is insufficient by itself for a resolution, but perhaps will serve as a collection point for additional data from others, or for pointing others to the circumvention I found.

Comment 1 Olivier Fourdan 2017-03-03 09:37:46 UTC
Ruling out Xwayland as comment 0 mentions a mix of Wayland native and Xwayland clients as being affected.

Moving to mutter, as this affects Wayland and the Wayland compositor (gnome-shell/mutter) routes input events to the Wayland clients.

Comment 2 Fedora End Of Life 2017-11-16 19:33:39 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:58:20 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.