Created attachment 1764847 [details] How the mouse cursor looks like on the internal display. No glitch. Description of problem: I have a HP Notebook with nvidia Optimus technology. So, there is an Intel Graphics card and a nvidia Quadro K1100M. I do not use the proprietary nvidia drivers. After the last upgrade to Kernel 5.11.7 my mouse cursor has a glitch, but only on the external display. The mouse cursor on the internal notebook disyplay is find. I'll attach two screenshots, which shows the issue. I use the KDE spin of Fedora 33. The session is a X session. How reproducible: Problem occurs always after logging in the user session. Actual results: Mouse cursor has a strange occurance on the second display. Expected results: The mouse cursor should look like the one on the internal display. Additional info: nvidia card: 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1) Intel: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) Operating System: Fedora 33 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.7-200.fc33.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4800MQ CPU @ 2.70GHz Memory: 15.1 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600
Created attachment 1764848 [details] Faulty mouse cursor on external disyplay. Glitch.
For me it is also happening with a single monitor (on a desktop PC - > HDMI -> screen), on Fedora33 LXDE, also after upgrading to the 5.11.7 kernel. qt.x86_64 1:4.8.7-57.fc33 @fedora qt5-qtbase.x86_64 5.15.2-2.fc33 @updates 07:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device 118b Flags: bus master, fast devsel, latency 0, IRQ 95, IOMMU group 16 Memory at fb000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=128M] Memory at e8000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nouveau Kernel modules: nouveau
By booting back to the previous kernel (5.10.23-200.fc33.x86_64) the problem does not occur. It was a single attempt. I have done no configuration modification between the boots.
I'm having the same problem with my nouveau driver after upgrading to kernel 5.11.7-200.fc33.x86_64 on my HP laptop, no external display. Rebooting into the previous kernel-5.10.23-200.fc33.x86_64 works fine. This happens with both GNOME and MATE. $ sudo lshw -class display *-display description: VGA compatible controller product: GK107GLM [Quadro K1000M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:32 memory:d8000000-d8ffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:4000(size=128) memory:c0000-dffff
Interesting: just tried to take a screenshot to show the mangled mouse pointer, but in the screenshot the pointer shows correctly! Also, this bug is marked as an issue with ssdm, but I'm pretty sure it's actually the nouveau driver.
Triaging to kernel
*** Bug 1941222 has been marked as a duplicate of this bug. ***
The following workaround corrects it for me. Tested with multiple reboots by randomly changing a bunch of nvidia-related settings between them: # dnf history info 85 | egrep -i '^(command line|\s+install)' Command Line : install akmod-nvidia Install egl-wayland-1.1.6-1.fc33.i686 @updates Install egl-wayland-1.1.6-1.fc33.x86_64 @updates Install elfutils-libelf-devel-0.183-1.fc33.x86_64 @updates Install kernel-devel-5.11.7-200.fc33.x86_64 @updates Install python-rpm-macros-3.9-14.fc33.noarch @updates Install python2-rpm-macros-3.9-14.fc33.noarch @updates Install rpm-build-4.16.1.2-1.fc33.x86_64 @updates Install rpmdevtools-9.3-3.fc33.noarch @updates Install zstd-1.4.9-1.fc33.x86_64 @updates Install akmods-0.5.6-26.fc33.noarch @fedora Install fakeroot-1.25.2-1.fc33.x86_64 @fedora Install fakeroot-libs-1.25.2-1.fc33.x86_64 @fedora Install kmodtool-1-41.fc33.noarch @fedora Install libglvnd-gles-1:1.3.2-2.fc33.i686 @fedora Install libglvnd-gles-1:1.3.2-2.fc33.x86_64 @fedora Install libglvnd-opengl-1:1.3.2-2.fc33.i686 @fedora Install libglvnd-opengl-1:1.3.2-2.fc33.x86_64 @fedora Install libvdpau-1.4-3.fc33.i686 @fedora Install patch-2.7.6-13.fc33.x86_64 @fedora Install python3-progressbar2-3.51.4-2.fc33.noarch @fedora Install python3-rpm-generators-11-11.fc33.noarch @fedora Install python3-utils-2.4.0-2.fc33.noarch @fedora Install xemacs-filesystem-21.5.34-38.20200331hge2ac728aa576.fc33.noarch @fedora Install akmod-nvidia-3:460.56-1.fc33.x86_64 @rpmfusion-nonfree-updates Install nvidia-settings-3:460.56-1.fc33.x86_64 @rpmfusion-nonfree-updates Install xorg-x11-drv-nvidia-3:460.56-1.fc33.x86_64 @rpmfusion-nonfree-updates Install xorg-x11-drv-nvidia-kmodsrc-3:460.56-1.fc33.x86_64 @rpmfusion-nonfree-updates Install xorg-x11-drv-nvidia-libs-3:460.56-1.fc33.i686 @rpmfusion-nonfree-updates Install xorg-x11-drv-nvidia-libs-3:460.56-1.fc33.x86_64 @rpmfusion-nonfree-updates
This is indeed a kernel issue; and yes switching to the binary nvidia driver will work around it, but that has other issues (like breaking on kernel upgrades). Bug 1941291 has more details and a link to a patch fixing this, so I'm marking this one as a duplicate. *** This bug has been marked as a duplicate of bug 1941291 ***