Description of problem: Sometimes, when I move the mouse, the cursor won't move. It is especially a problem if I haven't moved the mouse (and have typed) in the meantime. Sometimes when that happens (especially when the cursor is "stuck"), I'll see in journalctl: Jan 27 11:27:19 ascheel-p50 gnome-shell[2591]: libinput error: client bug: timer event5 debounce short: offset negative (-4ms) Jan 27 11:27:20 ascheel-p50 gnome-shell[2591]: libinput error: client bug: timer event5 debounce short: offset negative (-7ms) Version-Release number of selected component (if applicable): gnome-shell-3.34.3-1.fc31.x86_64 libinput-1.15.0-1.fc31.x86_64 kernel-5.4.13-201.fc31.x86_64 How reproducible: More frequent since this reboot. Steps to Reproduce: 1. Move mouse: see cursor move 2. Do something else (type) 3. Move mouse again: see cursor not move Actual results: Cursor sometimes doesn't move when the mouse was moved. Expected results: Cursor should always move when the mouse is moved. Additional info:
https://wayland.freedesktop.org/libinput/doc/latest/faqs.html#what-causes-the-timer-offset-negative-warning has an explanation of the cause of this particular warning. The root cause is actually a set of causes, see this long bugzilla discussion here: https://bugzilla.gnome.org/show_bug.cgi?id=745032 and the gitlab issue here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/749 But in short - this is a mutter/gnome-shell problem and the error message you see here is actually a sign that libinput too is affected by this bug.
Any ETA on when these will make it to Fedora 32? Sep 8 09:00:18 me kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Sep 8 09:00:18 me journal[3715]: ../clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Sep 8 09:07:17 me kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Sep 8 09:07:17 me journal[3715]: ../clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Sep 8 09:07:32 me kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Sep 8 09:07:32 me journal[3715]: ../clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Sep 8 09:11:15 me kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Sep 8 09:11:15 me journal[3715]: ../clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Sep 8 09:14:41 me journal[3715]: ../clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Sep 8 09:14:41 me kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Sep 8 09:21:49 me gnome-shell[3715]: libinput error: event7 - PixArt HP USB Optical Mouse: client bug: event processing lagging behind by 17ms, your system is too slow Sep 8 09:36:08 me gnome-shell[3715]: libinput error: event3 - Chicony HP Business Slim Keyboard: client bug: event processing lagging behind by 24ms, your system is too slow Sep 8 09:40:10 me cupsd[1226]: REQUEST localhost - - "POST / HTTP/1.1" 200 181 Renew-Subscription successful-ok Sep 8 09:48:38 me gnome-shell[3715]: libinput error: event3 - Chicony HP Business Slim Keyboard: client bug: event processing lagging behind by 29ms, your system is too slow
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.
[root@vulgar log]# cat /etc/redhat-release Fedora release 33 (Thirty Three) [root@vulgar log]# uname -a Linux vulgar.display.of.power 5.10.13-200.fc33.x86_64 #1 SMP Thu Feb 4 14:54:51 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux [root@vulgar log]# Feb 11 09:52:10 vulgar.display.of.power gnome-shell[157433]: libinput error: client bug: timer event5 debounce short: scheduled expiry is in the past (> Feb 11 09:52:44 vulgar.display.of.power kernel: general protection fault, probably for non-canonical address 0x80342e2716c0ae47: 0000 [#1] SMP PTI Feb 11 09:52:44 vulgar.display.of.power kernel: CPU: 2 PID: 157569 Comm: Xwayland Tainted: G W 5.10.7-200.fc33.x86_64 #1 Feb 11 09:52:44 vulgar.display.of.power kernel: Hardware name: System manufacturer System Product Name/P9X79 PRO, BIOS 4701 05/07/2014 Feb 11 09:52:44 vulgar.display.of.power kernel: RIP: 0010:kmem_cache_alloc_trace+0x7f/0x1e0 Feb 11 09:52:44 vulgar.display.of.power kernel: Code: 91 d2 75 49 8b 00 49 83 78 10 00 48 89 04 24 0f 84 54 01 00 00 48 85 c0 0f 84 4b 01 00 00 41 8b 4> Feb 11 09:52:44 vulgar.display.of.power kernel: RSP: 0018:ffffa30247d377b0 EFLAGS: 00010286 Feb 11 09:52:44 vulgar.display.of.power kernel: RAX: 80342e2716c0ae17 RBX: 0000000000000002 RCX: 80342e2716c0ae47 Feb 11 09:52:44 vulgar.display.of.power kernel: RDX: 0000000000f1e3ae RSI: 0000000000000dc0 RDI: 000000000002f0c0 Feb 11 09:52:44 vulgar.display.of.power kernel: RBP: ffff9518c0043a00 R08: ffff951befaaf0c0 R09: 0000000000000018 Feb 11 09:52:44 vulgar.display.of.power kernel: R10: ffff951b4a07ca48 R11: ffffa30247d37a20 R12: ffff9518c0043a00 Feb 11 09:52:44 vulgar.display.of.power kernel: R13: 0000000000000048 R14: ffffffffc04f753a R15: 0000000000000dc0 Feb 11 09:52:44 vulgar.display.of.power kernel: FS: 00007f6dd18e5a80(0000) GS:ffff951befa80000(0000) knlGS:0000000000000000 Feb 11 09:52:44 vulgar.display.of.power kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 11 09:52:44 vulgar.display.of.power kernel: CR2: 00007f6dd1856000 CR3: 0000000026a52006 CR4: 00000000000606e0 Feb 11 09:52:44 vulgar.display.of.power kernel: Call Trace: Feb 11 09:52:44 vulgar.display.of.power kernel: nvkm_mem_new_type+0xaa/0x2a0 [nouveau] Feb 11 09:52:44 vulgar.display.of.power kernel: nvkm_umem_new+0x132/0x220 [nouveau] Feb 11 09:52:44 vulgar.display.of.power kernel: nvkm_ioctl_new+0x129/0x1e0 [nouveau] Feb 11 09:52:44 vulgar.display.of.power kernel: ? nvkm_umem_search+0xe0/0xe0 [nouveau] Feb 11 09:52:44 vulgar.display.of.power kernel: nvkm_ioctl+0xde/0x180 [nouveau] Feb 11 09:52:44 vulgar.display.of.power kernel: nvif_object_ctor+0x11e/0x1c0 [nouveau] Feb 11 09:52:44 vulgar.display.of.power kernel: nvif_mem_ctor_type+0xc2/0x180 [nouveau] Feb 11 09:52:44 vulgar.display.of.power kernel: ? dma_coherent_ok+0x17/0xe0 Feb 11 09:52:44 vulgar.display.of.power kernel: ? ttm_dma_pool_get_pages+0x2e6/0x550 [ttm] Feb 11 09:52:44 vulgar.display.of.power kernel: ? cap_inode_getsecurity+0x230/0x230 Feb 11 09:52:44 vulgar.display.of.power kernel: ? security_capable+0x36/0x50 Feb 11 09:52:44 vulgar.display.of.power kernel: ? ttm_check_swapping+0x16/0x80 [ttm] Feb 11 09:52:44 vulgar.display.of.power kernel: nouveau_mem_host+0xf3/0x190 [nouveau] Feb 11 09:52:44 vulgar.display.of.power kernel: nouveau_sgdma_bind+0x30/0x80 [nouveau]