Bug 479002 - Wayland atomic mode-setting cursors not shown on vmwgfx driver
Summary: Wayland atomic mode-setting cursors not shown on vmwgfx driver
Status: RESOLVED DUPLICATE of bug 478487
Alias: None
Product: kwin
Classification: Plasma
Component: platform-drm (show other bugs)
Version: git master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-25 19:41 UTC by Stefan Hoffmeister
Modified: 2024-01-09 17:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Hoffmeister 2023-12-25 19:41:01 UTC
SUMMARY

When forcing on atomic mode-setting through `export KWIN_DRM_NO_AMS=0` on KDE Plasma 6 git master (beta2+) in a Wayland session, on VMware Workstation (vmwgfx kernel driver), no cursor is shown.

Looking at

`watch -n 1 "drm_info | grep -E 'Plane|Connector|FB_ID|\"CRTC'"`

suggests that the plane is assigned to the right CRTC, that the FB_ID changes. There is no applicable log output at level debug+.

STEPS TO REPRODUCE
1. force atomic mode-setting to on via `export KWIN_DRM_NO_AMS=0`
2. make sure that software cursors are _not_ on (i.e. _not_ KWIN_FORCE_SW_CURSOR=1)
3. log into Plasma Wayland session

OBSERVED RESULT

No cursor visible on screen, but system _acts_ as if there is a cursor present (clicks etc work)

EXPECTED RESULT

Cursor visible on screen.

ADDITIONAL INFORMATION

Note that right now forcing on of KWIN_DRM_NO_AMS is required due to the Linux kernel (virtual graphics drivers) lacking some capabilities in version 6.7.0-rc5. With Linux kernel 6.8 these capabilities will be present in the kernel and kwin will automatically enable atomic mode-setting.
Comment 1 Stefan Hoffmeister 2023-12-25 19:42:36 UTC
Note that for atomic mode-setting and "hardware" cursors to work on the VMware vmwgfx driver, a kernel patch is required to prevent kernel oopses, see https://bugs.kde.org/show_bug.cgi?id=478308
Comment 2 Zamundaaa 2024-01-09 17:14:48 UTC

*** This bug has been marked as a duplicate of bug 478487 ***