https://bugs.kde.org/show_bug.cgi?id=479634
Paul de Vrieze <paul.devri...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |paul.devri...@gmail.com
--- Comment #3 from Paul de Vrieze <paul.devri...@gmail.com> ---
I have a similar issue. In my case the cursor is visible properly in 5.91.0. In
5.92.0 the cursor is only visible on the (primary) laptop screen that is driven
by an Intel iGPU, but not on the external displays connected to the NVidia GPU.
In my case I tried setting both WLR_NO_HARDWARE_CURSORS=1 and
KWIN_FORCE_SW_CURSOR=1 in which the problem didn't go away (Reverting to 5.91.0
on an otherwise RC1 install "fixes" things, even with the environment variables
still set.
In dmesg I have the message: "[drm] [nvidia-drm] [GPU ID 0x00000100]
Framebuffer memory not appropriate for scanout". It also seems related to
https://forums.developer.nvidia.com/t/hardware-cursor-is-not-working-on-wayland-drm-sessions/261853
--
You are receiving this mail because:
You are watching all bug changes.
