Description of problem:
When logged into gnome-shell under Xorg on a fully-updated Fedora 23 system, the mouse cursor suddenly becomes invisible when entering into the activities overview, or when interacting with the activities toolbar.
Version-Release number of selected component (if applicable):
The problem appears to be caused by the update to mutter-3.18.3-1.fc23
Steps to Reproduce:
1. Log in to gnome-shell.
2. Enter activities overview.
3. Observe mouse cursor has disappeared.
Invisible mouse cursor.
Mouse cursor should remain visible.
I solved this problem for myself by downgrading mutter (dnf downgrade mutter)
This version is running currently without any problems: mutter-3.18.1-4.fc23
I confirm, I had the same problem, I could also not see the cursor on the top menubar.
Downgrading mutter also fixed the problem.
Same here, downgrading mutter solves the issue. It is a critical bug for non-tech users.
This looks like a duplicate of Bug 1315590.
*** Bug 1315590 has been marked as a duplicate of this bug. ***
I'm seeing this on a desktop:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
and my Lenovo T530:
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [NVS 5400M] (rev a1)
It was also reported on the following hardware in Bug 131590:
Lenovo M30-70 laptop with i915 graphics (Intel Corporation Haswell-ULT Integrated Graphics Controller).
In my PC with a radeon card I don't have this problem.
# rpm -q mutter
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870]
For reference, this is the hardware configuration I am running which is affected by this problem:
$ dmesg | grep -i macbookpro
[ 0.000000] DMI: Apple Inc. MacBookPro12,1/Mac-E43C1C25D4880AD6, BIOS MBP121.88Z.0167.B15.1510261437 10/26/2015
$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
I am happy to provide any additional information as requested.
*** This bug has been marked as a duplicate of bug 1316010 ***