[Bug 1117833] New: Wayland: briefffffffffff unresponsivvvvvvvvvvvveness and repeated keys
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833 Bug ID: 1117833 Summary: Wayland: briefffffffffff unresponsivvvvvvvvvvvveness and repeated keys Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: lpechacek@suse.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com CC: david.mulder@suse.com Found By: --- Blocker: --- The problem I'm observing is well described at https://forum.antergos.com/topic/9533/key-repeats-and-an-unresponsive-waylan... . On a fresh TW installation with Wayland, the desktop briefly freezes during typing and when it comes back the last character is repeated many times. This is not isolated to a single application. I've seen this behavior with VirtualBox, Chromium, GNOME Terminal and GVim. TTTTTTTTThe system log is filling with messages like this: Nov 29 17:16:33 fmn org.gnome.Shell.desktop[1914]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Nov 29 17:16:33 fmn org.gnome.Shell.desktop[1914]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Nov 29 17:16:33 fmn org.gnome.Shell.desktop[1914]: libinput error: client bug: timer event1 keyboard: offset negative (-372ms) Nov 29 17:16:33 fmn org.gnome.Shell.desktop[1914]: Window manager warning: last_user_time (251082637) is greater than comparison timestamp (251082073). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Nov 29 17:16:33 fmn org.gnome.Shell.desktop[1914]: Window manager warning: 0x2000001 (Enter Bug:) appears to be one of the offending windows with a timestamp of 251082637. Working around... Hardware is Lenovo X260. More details can be provided upon request. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c1
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c4
Michal Srb
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c5
Libor Pechacek
In gdm you can select GNOME sessions running on Xorg or just a windowmanager, which does not support Wayland (like icewm, xfce).
Took some time to find the switch but I succeeded in starting an Xorg based session. I've been using it for the whole day today without a single repetition. There are also no libinput error messages in system log. If you have more debugging suggestions, I'l be happy to perform the data collection. (In reply to Michal Srb from comment #4)
I am trying to reproduce it on my laptop with Tumbleweed - so far it happened to me only once. It was in gnome-shell (wayland) and it happened inside xterm, so X application tunneling thru Xwayland.
Thanks, Michal, for looking into it. On my side the issue appears in waves. Mostly there are no problems and only occasionally the system becomes sluggish and the key repeat trouble triggers. Looks like something is running in background but I haven't yet investigated.
The applications you named - VirtualBox, Chromium, GNOME Terminal and GVim - I think they all use Xwayland except for GNOME Terminal, which should use wayland directly.
It is possible that also VirtualBox is using Wayland directly as it is Qt based and has the plugin built in. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Felix Zhang
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c6
Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c7
--- Comment #7 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c8
--- Comment #8 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c9
--- Comment #9 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c10
Dennis Irrgang
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c11
--- Comment #11 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c12
--- Comment #12 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Emiliano Langella
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Michiel Janssens
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Oliver Kurz
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c13
Atri Bhattacharya
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Michiel Janssens
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c14
Atri Bhattacharya
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c15
--- Comment #15 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c16
--- Comment #16 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c17
--- Comment #17 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Bruce Rogers
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c21
--- Comment #21 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c22
--- Comment #22 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c26
--- Comment #26 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c27
--- Comment #27 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c28
--- Comment #28 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c30
--- Comment #30 from Victor Zhestkov
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c34
--- Comment #34 from Libor Pechacek
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833#c35
--- Comment #35 from Libor Pechacek
This might be related to bug#1112824
Having read the mentioned bug, I confirm that bug 1112824, comment 103 (last paragraph) and bug 1112824, comment 115 do describe behavior I'm seeing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Libor Pechacek
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Tomasz Witowski
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Roy Lee
http://bugzilla.opensuse.org/show_bug.cgi?id=1117833
Roscoe Brooks
participants (1)
-
bugzilla_noreply@novell.com