FS#52969 - [libinput] XWayland server becomes unresponsive on gnome shell
Attached to Project:
Arch Linux
Opened by CubeTheThird (CubeTheThird) - Wednesday, 15 February 2017, 01:33 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 06 September 2019, 19:59 GMT
Opened by CubeTheThird (CubeTheThird) - Wednesday, 15 February 2017, 01:33 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 06 September 2019, 19:59 GMT
|
Details
Description:
After the recent update to package version 1.19.1-2, running Gnome Shell on Wayland will randomly become unresponsive. All keyboard and mouse input appears to stop (the Caps Lock light does not even turn on), and the display becomes frozen. The system itself is still running, as I am able to properly shutdown and reboot using my PC's power button, and applications running appear to continue execution (e.g. audio keeps playing). In the system's journals, the only seemingly useful error message I've uncovered is: org.gnome.Shell.desktop[958]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! While I cannot guarantee the recent update is the cause of this issue, it seems to have manifested after its installation. I have also yet to find a pattern to the cause, as I've had different applications running when it occurs. Additional info: Xorg-server (etc.) version 1.19.1-2 gnome-shell 3.22.2+18+gdf7727a-1 |
This task depends upon
- kernel
- libinput
- compositor (weston, mutter, etc).
Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Additionnal information that might help track the issue:
the freeze only happens when I input japanese characters.
For example, let's say I input the letters arigatou. The japanese input software will then propose me a list of japanese characters to select from. I can iterate that list with the arrow keys or the mouse and chose the appropriate writing.
This is the only time I have the freeze: when I select the appropriate writing. The freeze, however, seems random.
When it happens my laptop is unresponsive to keyboard and mouse input, and I have to hard reset. My journalctl logs contain the same error message as in the bug description, repeated many times per second, e.g.
Oct 03 13:57:02 march org.gnome.Shell.desktop[1340]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Oct 03 13:57:02 march org.gnome.Shell.desktop[1340]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Oct 03 13:57:02 march org.gnome.Shell.desktop[1340]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Oct 03 13:57:02 march org.gnome.Shell.desktop[1340]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Oct 03 13:57:02 march org.gnome.Shell.desktop[1340]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Oct 03 13:57:02 march org.gnome.Shell.desktop[1340]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
I guess it could be an ibus or ibus-anthy bug, but googling for the error message lead me here, so I thought I'd chime in.
I had a go at finding a reproducible case by inputting lots of Japanese characters and continuously cycling through the list of completions, but was not able to reproduce.
My version info:
linux-lts 4.9.52-1
xorg-server 1.19.3-3
wayland 1.14.0-1
gnome-shell 3.24.3-1
ibus 1.5.16-1
ibus-anthy 1.5.9-1
Unfortunately, I still do not manage to find a precise reproducible test case and it is still very random. I might be able to type loads of japanese text without any problem, and some other days, I might have many freeze in a short time.
reaffecting the bug to libinput
déc. 13 10:43:36 frcls4524 org.gnome.Shell.desktop[962]: Window manager warning: last_focus_time (88409013) is greater than comparison timestamp (88408999). This most likely represents a buggy client sending
déc. 13 10:43:30 frcls4524 org.gnome.Shell.desktop[962]: libinput error: libinput bug: timer event3 debounce short: offset negative (-190257)
déc. 13 10:43:30 frcls4524 org.gnome.Shell.desktop[962]: libinput error: libinput bug: timer event3 debounce: offset negative (-150693)
déc. 13 10:48:24 frcls4524 org.gnome.Shell.desktop[962]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
This problem seems appear when I switch from Nvidia drivers to nouveau.
linux 4.14.4-1
gnome-shell 3.26.2+9+ga3736d3a3-1
wayland 1.14.0-1
mesa 17.2.6-1
libinput 1.9.3-1
févr. 21 10:47:07 frcls4524 org.gnome.Shell.desktop[930]: libinput error: client bug: timer event3 debounce short: offset negative (-14ms)
févr. 21 10:47:07 frcls4524 org.gnome.Shell.desktop[930]: libinput error: client bug: timer event3 debounce: offset negative (-1ms)
févr. 21 10:11:19 frcls4524 org.gnome.Shell.desktop[930]: Window manager warning: last_user_time (76152069) is greater than comparison timestamp (76152041). This most likely represents a buggy client sending
But no more screen frozen.
linux 4.15.3-2
gnome-shell 3.26.2+14+g64c857e3f-1
wayland 1.14.0-1
mesa 17.3.4-1
libinput 1.10.0-1
Jan 30 18:22:38 march org.gnome.Shell.desktop[1314]: libinput error: libinput bug: timer event16 debounce: offset negative (-4386)
Jan 30 18:22:38 march org.gnome.Shell.desktop[1314]: libinput error: libinput bug: timer event16 debounce short: offset negative (-17425)
Jan 30 18:23:03 march kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Jan 30 18:23:03 march kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
Jan 30 18:30:22 march systemd[1]: Starting system activity accounting tool...
Jan 30 18:30:22 march systemd[1]: Started system activity accounting tool.
Jan 30 18:31:54 march org.gnome.Shell.desktop[1314]: libinput error: libinput bug: timer event16 debounce short: offset negative (-6890)
-- Reboot --
As far as I can tell from looking at pacman.log, these are the packages I had installed at the time of the crash. I've since upgraded linux-lts, xorg-server, and mesa.
linux-lts 4.9.78-1
gnome-shell 3.26.2+14+g64c857e3f-1
xorg-server 1.19.6-2
wayland 1.14.0-1
mesa 17.3.3-1
libinput 1.9.4-1
ibus 1.5.17-1
At the time of writing, these are the two most recent log messages in my journal. I see they now say "client bug" rather than "libinput bug", so I guess this is a problem with a buggy client? Other logs seem to indicate it's probably Chrome.
Mar 21 10:50:22 march org.gnome.Shell.desktop[27924]: libinput error: client bug: timer event16 debounce: offset negative (-10ms)
Mar 21 10:50:22 march org.gnome.Shell.desktop[27924]: libinput error: client bug: timer event16 debounce short: offset negative (-23ms)
Have you a nvidia video card with nouveau driver?
For me, this problem seems to disappear with nvidia drivers and appear again with nouveau driver
I suspect your last question was for Eduardo, but, for what it's worth, I don't have an nvidia card or drivers. I have a thinkpad X201 with built-in intel chipset graphics.
Just open up a video, click multiple times the key 'F'. It toggles fullscreen mode.
At some point everything is being freezed.
Although, I'm able to restore things by terminating my session via ssh.
htop shows that gnome-shell and Xwayland are going crazy and load CPU to almost maximum.
If I kill mplayer application the freezing doesn't go away.
Need to restart gnome-shell as a whole.