Description of problem: Mouse cursor disappears under Gnome top bar, Dock, window switching control, Activities fullscreen mode. Version-Release number of selected component (if applicable): Wayland, + info: OS: Fedora 30 Thirty Kernel: x86_64 Linux 5.2.9-200.fc30.x86_64 Resolution: 1920x1080 DE: GNOME WM: GNOME Shell WM Theme: GTK Theme: Adwaita-dark [GTK2/3] Icon Theme: Adwaita Font: Iosevka 10 GPU: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) How reproducible: It depends on nothing. But to enable cursor again you must click with mouse left button on top bar when one active window is in fullscreen mode. This action leads to change cursor pointer to axis (or cross) mode and start dragging fullscreened window. Steps to Reproduce: 1. I don't know, just work and wait. It constantly repeats. I would provide additional info if you tell me what you need and how do I get it.
I've been having this happen, too, but I can't get it to happen consistently. Just now, I closed all (two) windows, LibreOffice Calc and PCManFM, using <Alt>F4 and the mouse pointer disappeared again. But trying to get it to happen again was unsuccessful.
Duplicate of #1747985 ? Also, this is happening to me as well on Fedora 30 with a clean install.
Upstream issue tracker appears to be https://gitlab.gnome.org/GNOME/gnome-shell/issues/1165 with quite a few comments, workarounds and observations posted by users of many distros. They seem to peg it as owning to Kernel 5.2+ and downgrading helps, which would probably target an interaction of the Intel DRM driver. (I am using 5.2.13 and Intel integrated graphics.) @bberg suggests mutter needs to check a return code and points to a specific line of code in mutter: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1165#note_600721 There are reports that it is fixed in kernel 5.3+; one user claims 5.2.13 fixed it for them, but I still have the problem on that kernel version. (They are using Arch, I am on Fedora.)
Yep: $ lspci | grep -i graph 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c) $ uname -r 5.2.11-200.fc30.x86_64
I just got a kernel update and the problem is still occurring: $ uname -r 5.2.13-200.fc30.x86_64
I just updated from kernel 5.13 to kernel 5.15 and it appears to have fixed the problem.
It's back. never mind. Prior to the update, the glitch usually occured as soon as I logged in; This time, it took about 40 minutes for my cursor to disappear. It definitely seems like updating has improved things. It's worth nothing that, at least for me, the issue only occurs on wayland; I switched to xorg as a workaround, but that's obviously not ideal. I'm using mesa 19.6 on a celeron N3160 with intel hd graphics 400.
(In reply to Colby Jenn from comment #6) > I just updated from kernel 5.13 to kernel 5.15 and it appears to have fixed > the problem. I think you likely mean 5.2.13 to 5.2.15. I saw some reports that it was fixed in 5.3.x, but that hasn't hit Fedora's main repositories yet. --js
Switched to using 5.3.2 Fedora Vanilla Kernel. Problem goes away. Hopefully this means that when the 5.3.2 kernel becomes mainstream this issue will be resolved. See https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories#What_kernel_versions_do_the_repos_currently_contain.3F for information to decide if this "solution" meets with your needs. My computer is quite old and doesn't have UEFI. As such, I can easily boot these unsigned kernels.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.