OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
gpu-drivers low common DISPUTE

Fix choppy 60 fps bar and menu animations on NVIDIA high-refresh monitors

omarchynvidiadesktophyprlandquickshell
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

The cause holds. omarchy#7268 (open) quotes the qtwayland check that sets m_supportsThreading false when the EGL vendor is NVIDIA and XDG_CURRENT_DESKTOP is set, cites QTBUG-95817, shows basic render loop on an RTX 4090 and RTX 5080 against threaded render loop on Mesa, and measures 62 versus 240 fps with QSG_RHI_BACKEND=vulkan. Omarchy sets XDG_CURRENT_DESKTOP=Hyprland itself in /usr/share/omarchy/default/hypr/envs.lua, so every Omarchy session meets the condition. grep of /usr/share/omarchy on 4.0.4-1 finds no QSG_ variable, and the fix PR omarchy#7269 is still open. The lock-screen crash in the symptom comes from a 2026-08-26 comment on the same issue (Omarchy 4.0.1, RTX 4070 Super), and the shell runs as a process named quickshell, so the verify command works. One gap in the fix: it says 'run the shell on Qt's Vulkan backend', but hl.env sets the variable for the whole session, so every Qt Quick app launched afterwards also switches to Vulkan. The issue's PR deliberately scopes it to the shell and to machines where NVIDIA is the primary display GPU. The fix now states the wider scope and how to undo it. It keeps logging out rather than the issue's omarchy restart shell, which can re-lock a session whose locker has died. Not exercised: no NVIDIA desktop here.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

On an NVIDIA GPU with a 144 Hz or 240 Hz monitor, Hyprland's window animations are smooth but everything the Omarchy shell draws (bar, tray drawer, menus, OSDs) moves at about 60 fps and looks choppy. Some NVIDIA users also see the lock screen crash with QWaylandGLContext::makeCurrent: eglError: 0x3003 followed by FATAL: Failed to initialize graphics backend for OpenGL.

Cause

Qt disables threaded OpenGL rendering on the proprietary NVIDIA driver whenever XDG_CURRENT_DESKTOP is set, as a workaround for QTBUG-95817. Qt Quick then uses its basic render loop, which drives animations from a roughly 16 ms timer with no vsync awareness, so the whole shell is capped near 60 fps. QSG_INFO=1 reports basic render loop on NVIDIA and threaded render loop on Mesa (omarchy#7268, Omarchy 4.0.0, RTX 4090 and RTX 5080). With the Vulkan RHI backend the threaded loop is Qt's default everywhere. Omarchy 4.0.4 still sets no QSG_RHI_BACKEND.

Fix

Run Qt Quick on its Vulkan backend. In ~/.config/hypr/hyprland.lua, below require("default.hypr.omarchy"):


-- Qt Quick: Vulkan backend restores the threaded render loop on NVIDIA
hl.env("QSG_RHI_BACKEND", "vulkan")

Log out and back in so the shell inherits it.

This sets the variable for the whole session, not only the shell, so every Qt Quick app you launch afterwards also renders through Vulkan. Omarchy's proposed fix (PR omarchy#7269, still open on 2026-10-05) applies it to the shell only. If another Qt app misbehaves after the change, delete the line and log out and back in.

Use this only when the NVIDIA GPU drives the display. On a hybrid laptop where the iGPU drives the panel, the shell already gets Mesa's threaded loop, and the issue author advises against forcing Vulkan there.

Verify

tr '\0' '\n' < /proc/$(pgrep -x quickshell)/environ | grep QSG_RHI_BACKEND prints QSG_RHI_BACKEND=vulkan, and shell animations look as smooth as window animations.

Sources

omarchy-shell-animations-60fps-nvidia-basic-render-loop