Description of problem: Mouse cursor often stops rendering on "top level" windows/surfaces. Requires toggling from two displays back to one and back to restore. Happens several times a day. Version-Release number of selected component (if applicable): 3.32.2-2.fc30 How reproducible: Several times a day, no particular pattern. Steps to Reproduce: 1. Using two displays: Laptop panel and (via dock DisplayPort) desktop screen. Only one workspace across the two displays. 2. At some point I notice that hovering over e.g. the status bar, icons will be highlighted but the mouse pointer no longer renders in that area. 3. When this happens another way to notice is that the mouse pointer doesn't render when I use the left Windows key to get overview mode. The windows display and are highlighted correctly as I move the mouse, but the pointer doesn't show up at all in this case. 4. I've settled on this workaround: Windows → type "display" → select Display settings → select single display, apply → revert settings back to two displays. This will restore mouse pointer behavior until next time. I've see this up to just a couple minutes apart. Actual results: Mouse pointer frequently disappears from parts of the display. Expected results: This is a regression, didn't use to happen until very recently. I did upgrade F29-F30 recently but my impression is that this started after the distro upgrade. Additional info: This stack trace is always present in the journal when this happens: Aug 08 09:19:27 vimes gnome-shell[3177]: JS ERROR: TypeError: this._workspacesViews[i] is undefined _updateWorkspacesFullGeometry@resource:///org/gnome/shell/ui/workspacesView.js:714:13 setWorkspacesFullGeometry@resource:///org/gnome/shell/ui/workspacesView.js:704:9 setWorkspacesFullGeometry@resource:///org/gnome/shell/ui/viewSelector.js:293:9 _updateWorkspacesGeometry@resource:///org/gnome/shell/ui/overviewControls.js:456:9 vfunc_allocate@resource:///org/gnome/shell/ui/overviewControls.js:389:9 _updateWorkspacesViews@resource:///org/gnome/shell/ui/workspacesView.js:637:13 show@resource:///org/gnome/shell/ui/workspacesView.js:557:9 show@resource:///org/gnome/shell/ui/viewSelector.js:268:9 _animateVisible@resource:///org/gnome/shell/ui/overview.js:527:9 show@resource:///org/gnome/shell/ui/overview.js:513:9 toggle@resource:///org/gnome/shell/ui/overview.js:636:13 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:190:13
I've reproduced this just now waking up the laptop from suspend. However my desktop had been configured to only use one display - the external one. I haven't seen the stack trace above this time. Couple of entries in the log that look potentially interesting: Aug 09 08:33:09 vimes gnome-shell[3225]: Device Current State: 100 Aug 09 08:33:09 vimes gnome-shell[3225]: Could not delete runtime/persistent state file: Error removing file /run/user/1000/gnome-shell/runtime-state-LE.:0/screenShield.locked: No such file> Aug 09 08:35:19 vimes org.gnome.Shell.desktop[3225]: libinput error: client bug: timer event21 debounce short: offset negative (-0ms)
Probably related to upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1165
Another workaround is to force gnome-shell to change the pointer shape, for example, by running a new application from the activities screen or by launching gnome-control-center from the top-right menu, then it gets restored for a while until the bug happens again.
I get this bug on ThinkPad X280 laptop without using external monitors. After a recent update after a suspend the mouse cursor became invisible on Gnome shell surfaces on internal laptop display. The workaround from the comment 3 works.
It looks like a kernel regression in 5.2. I run the last 2 days with 5.1.8-300 kernel and the bug disappears.
are these issues not the same: https://bugzilla.redhat.com/show_bug.cgi?id=1739832 https://bugzilla.redhat.com/show_bug.cgi?id=1738614 https://bugzilla.redhat.com/show_bug.cgi?id=1739169 for me this issue is still occurring in Fedora 30. I have it for a month now on 3 machines and definitely started experiencing this after an update in begin August. I am updating all my machines daily. the workaround of opening a new application in Activities is the best for me. my question is if these bugs should not be merged and the priority raised, since it is basic functionality for the GUI/desktop and a regress
There have been reports that this is caused by recent kernel changes; and from other reports it seems that this is fixed by the 5.3 kernels. If you have this bug, please try installing a 5.3 kernel and report back to us if that helps. I suggest trying this kernel: https://koji.fedoraproject.org/koji/buildinfo?buildID=1375052 Yes this is a F31 kernel, but those work fine on F30. For instructions for installing a kernel directly from koji (our build system) see: https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt
*** This bug has been marked as a duplicate of bug 1738614 ***