Description of problem: After upgrading to Fedora 33, I've started getting freezes in Sublime Text 3 and in Terminator when running on X11. It's just for a few seconds where it seems that screen stops updating and only mouse moves are redrawn. No clear reproduction is available, only I'm always typing something at that point, it sometimes happens when I use a CTRL+<key> combination, sometimes just typing. Only those two programs are visibly affected for me. Quick workaround is to jump to overview and back, than fixes the issue that one time. In a few cases just moving the mouse for a few seconds helped. Before the upgrade I've spent a full work day on Fedora 32 with no issues, thus I think it's not directly hardware-related. It also doesn't appear to happen in Firefox or Slack. This happens on GNOME, X11, Lenovo T490 attached to a dock brick and 1 external monitor (only the monitor is used, laptop is closed). Intel iGPU. Version-Release number of selected component (if applicable): * gnome-shell-3.38.1-2.fc33.x86_64 * sublime-text-3210-1.x86_64 * terminator-2.0.1-1.fc33.noarch * other users have confirmed in other terminal emulators, I don't know the specific packages and versions How reproducible: Between 1x per 10 seconds to 1x per 10 minutes. Steps to Reproduce: 1. Open one of the affected programs 2. Work as usual (CTRL+R has heightened chance of causing the issue in Terminator) Actual results: Visual lag, need to apply the Overview workaround Expected results: Every keypress is displayed immediately Additional info: A few other users have confirmed this on Reddit: https://www.reddit.com/r/Fedora/comments/jnc85b/shorttime_freezes_in_sublime_text_and_terminator/
Based on journalctl --follow, the most common type of log shown during these freezes is this: Nov 04 10:56:38 HOSTNAME /usr/libexec/gdm-x-session[4345]: (EE) client bug: timer event4 debounce: scheduled expiry is in the past (-8ms), your system is too slow Nov 04 10:56:38 HOSTNAME /usr/libexec/gdm-x-session[4345]: (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-21ms), your system is too slow Nov 04 10:56:57 HOSTNAME /usr/libexec/gdm-x-session[4345]: (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-10ms), your system is too slow Nov 04 10:57:17 HOSTNAME /usr/libexec/gdm-x-session[4345]: (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-9ms), your system is too slow Nov 04 10:57:18 HOSTNAME /usr/libexec/gdm-x-session[4345]: (EE) event4 - Logitech MX Vertical: client bug: event processing lagging behind by 27ms, your system is too slow Nov 04 10:57:19 HOSTNAME /usr/libexec/gdm-x-session[4345]: (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-3ms), your system is too slow Nov 04 10:57:22 HOSTNAME /usr/libexec/gdm-x-session[4345]: (EE) client bug: timer event4 debounce: scheduled expiry is in the past (-9ms), your system is too slow Nov 04 10:57:22 HOSTNAME /usr/libexec/gdm-x-session[4345]: (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-22ms), your system is too slow Versions of possibly related packages: gdm-3.38.1-1.fc33.x86_64 libinput-1.16.1-1.fc33.x86_64 solaar-1.0.4-1.fc33.noarch
In case it makes a difference - I use Logitech MX Vertical mouse (as seen in the journalctl output) over a Unifying dongle. One of the affected users on Reddit confirmed he also uses a Logitech mouse, and he can reproduce the freezing issue in gnome-terminal.
When testing in Wayland session, I don't get any freezes, even though very similar logs are still visible in journalctl: Nov 06 12:03:13 HOSTNAME gnome-shell\[13673\]: libinput error: event5 - Logitech MX Vertical: client bug: event processing lagging behind by 25ms, your system is too slow Nov 06 12:03:13 HOSTNAME gnome-shell\[13673\]: libinput error: client bug: timer event5 debounce short: scheduled expiry is in the past (-9ms), your system is too slow Nov 06 12:04:34 HOSTNAME gnome-shell\[13673\]: libinput error: event6 - Logitech K520: client bug: event processing lagging behind by 17ms, your system is too slow Nov 06 12:04:40 HOSTNAME gnome-shell\[13673\]: libinput error: event5 - Logitech MX Vertical: client bug: event processing lagging behind by 31ms, your system is too slow
Some of the freezes on X11 seem to coincide with these logs: Nov 11 14:29:28 HOSTNAME systemd[3127]: Starting Tracker metadata extractor... Nov 11 14:29:28 HOSTNAME tracker-extract[34024]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus. Nov 11 14:29:28 HOSTNAME systemd[3127]: Started Tracker metadata extractor. Also, some of the freezes are time-limited (a few seconds) and disappear on their own, while others appear to persist until the mouse cursor leaves the current window (or some of its parts, in Terminator it seems enough to move over to another terminal split within the same window and tab).
This sounds like https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3369 which seems to have been caused by an extension.
Thanks for the link! However, I have the same comment as in that ticket - the issue reproduces in Terminator even with all extensions disabled. I'll try to come up with a reproduction scenario different than "work for an hour". BTW, should I switch to the GitLab ticket or is this one OK?
Seems some users in the upstream issue could reproduce without extensions, but I have yet to have managed. I think posting upstream would be great if you find any better reproduction steps. There is also some instructions how to allow me to investigate without reproducing myself, see the comment about `WAYLAND_DEBUG=1`.
I've noticed there's now gnome-shell-3.38.1-3.fc33.x86_64 - I can still reproduce the issue on that version (I'd love to provide Wayland debug logs, but it's X11-specific for me unfortunately).
Not that a +1 would be very helpful, but I run into the same issue on F33 with terminator-2.1.0-1.fc33.noarch I upgraded my system yesterday. - Andreas
For completeness: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3369 lists several workarounds, such as using cairo clock or https://github.com/justinrdonnelly/wandering-pixel
FEDORA-2021-4fe7b3bb76 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4fe7b3bb76
FEDORA-2021-4fe7b3bb76 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4fe7b3bb76` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4fe7b3bb76 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-4fe7b3bb76 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.