Stop a shell plugin's Qt MediaPlayer holding the NVIDIA dGPU awake on a hybrid Omarchy laptop
omarchy#12506 (open) supports the handle list, the 15 second suspend after stopping the shell, and the two QT_FFMPEG_*_HW_DEVICE_TYPES=, variables. The shell process is quickshell -n -p /usr/share/omarchy/shell, started by hl.exec_cmd("omarchy-launch-shell") in /usr/share/omarchy/default/hypr/autostart.lua, so it inherits hl.env values. The record misattributes the holder to Omarchy itself. grep of /usr/share/omarchy/shell on 4.0.4-1 finds no Qt Multimedia MediaPlayer anywhere. lock-explorer is a third-party plugin (github.com/SirJul1337/omarchy-lock-explorer) installed under ~/.config/omarchy/plugins/, and the issue's own minimal repro shows a shell with no MediaPlayer opens no NVIDIA handles. A stock Omarchy shell does not hold the dGPU this way, so the title and cause misled every hybrid-laptop reader, and common overstates it. The plugin's current designs/UnlockClip.qml loads its player through a Loader only while its window is mapped, with a comment naming this exact problem, so updating the plugin is the first fix (read from source, not tested). The env-var fix stays as the fallback, now with the scope stated correctly: it affects every Qt app in the session. Uses omarchy plugin list/update/disable, which exist in /usr/share/omarchy/bin. Frequency lowered to rare. Not exercised: no hybrid NVIDIA laptop here.
Symptom
On an Intel or AMD plus NVIDIA laptop whose session renders on the iGPU, battery drains fast even at idle. nvidia-smi lists no processes, yet cat /sys/bus/pci/devices/0000:01:00.0/power/runtime_status stays active. sudo fuser -v /dev/nvidia0 /dev/nvidiactl shows quickshell holding about 19 handles alongside Hyprland.
Cause
The Omarchy shell is Quickshell, started as quickshell -n -p /usr/share/omarchy/shell by omarchy-launch-shell. Stock Omarchy 4.0.4 shell code constructs no Qt Multimedia MediaPlayer, but a user-installed shell plugin under ~/.config/omarchy/plugins/ can. The reported case is the third-party lock-explorer plugin (SirJul1337/omarchy-lock-explorer), which built its unlock-clip MediaPlayer eagerly. Constructing a MediaPlayer makes Qt's FFmpeg backend enumerate hardware encode and decode devices, which opens /dev/nvidia0, /dev/nvidiactl, /dev/nvidia-uvm, /dev/nvidia-modeset and a render node. Open handles block runtime D3, so the dGPU never suspends (omarchy#12506, Omarchy 4.0.4, quickshell 0.3.1). A minimal quickshell config with one MediaPlayer {} reproduces all 19 handles, and with none it opens none. Stopping the shell let the GPU suspend within about 15 seconds on the reporter's machine. Setting Qt's FFmpeg hardware device lists to empty stops the probing. The plugin's current source creates its player through a Loader only while its window is shown, so an up-to-date copy should no longer hold the GPU at idle. This is a different holder from apps rendering on the dGPU, which the record nvidia-dgpu-no-runtime-d3-battery-drain covers along with the RTD3 setup itself.
Fix
Confirm the shell is the holder:
sudo fuser -v /dev/nvidia*
cat /sys/bus/pci/devices/0000:01:00.0/power/runtime_status # adjust the PCI address from lspci -D
Find which installed plugin creates a MediaPlayer. The stock Omarchy shell has none:
omarchy plugin list
grep -rl 'MediaPlayer' ~/.config/omarchy/plugins/
Update that plugin, using the id omarchy plugin list prints. The current lock-explorer source only creates its player while its window is shown:
omarchy plugin update <id>
If it still holds the GPU after you log out and back in, disable it:
omarchy plugin disable <id>
If you need to keep a plugin that still creates a player at start, disable Qt's FFmpeg hardware backends for the session instead. In ~/.config/hypr/hyprland.lua, below require("default.hypr.omarchy"):
-- Keep Qt Multimedia from opening the NVIDIA dGPU at shell start
hl.env("QT_FFMPEG_DECODING_HW_DEVICE_TYPES", ",")
hl.env("QT_FFMPEG_ENCODING_HW_DEVICE_TYPES", ",")
The shell is started by omarchy-launch-shell from /usr/share/omarchy/default/hypr/autostart.lua and inherits hl.env values, so log out and back in to apply it.
These variables apply to every Qt app in the session, not only the shell: Qt Multimedia video decode and encode fall back to software. Browsers and mpv use their own decoders and are unaffected.
Verify
After logging back in, sudo fuser -v /dev/nvidia* no longer lists quickshell, and within about 15 seconds runtime_status reads suspended.