From 54473f03baf4bb850683602379b7fdee185f9b3c Mon Sep 17 00:00:00 2001 From: Vlad Zahorodnii Date: Wed, 5 Jun 2024 15:15:16 +0300 Subject: [PATCH] Re-enable hardware cursor on intel devices My recent testing has shown that screen freezes when moving the cursor cannot be observed anymore. Maybe the issue has been fixed upstream by some unrelated change. Either way, let's re-enable the hardware cursor to gather some feedback. --- src/compositor_wayland.cpp | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/src/compositor_wayland.cpp b/src/compositor_wayland.cpp index 691d9a5326..6b193f0912 100644 --- a/src/compositor_wayland.cpp +++ b/src/compositor_wayland.cpp @@ -378,11 +378,7 @@ void WaylandCompositor::addOutput(Output *output) cursorLayer->setParent(workspaceLayer); cursorLayer->setSuperlayer(workspaceLayer); - // Software cursor is forced for intel devices because there are screen stuttering issues with hardware cursor, - // possibly a kernel driver bug. Remove the workaround when https://gitlab.freedesktop.org/drm/intel/-/issues/9571 is fixed. - static bool forceSoftwareCursorIsSet; - static const bool forceSoftwareCursor = qEnvironmentVariableIntValue("KWIN_FORCE_SW_CURSOR", &forceSoftwareCursorIsSet) == 1 - || (!forceSoftwareCursorIsSet && scene()->openglContext() && scene()->openglContext()->glPlatform()->isIntel()); + static const bool forceSoftwareCursor = qEnvironmentVariableIntValue("KWIN_FORCE_SW_CURSOR") == 1; auto updateCursorLayer = [this, output, cursorLayer]() { const Cursor *cursor = Cursors::self()->currentCursor();