INC-2026-03-27: Investigation

Investigation

Initial Triage

nvidia-smi
Output
|   0  NVIDIA GeForce RTX 5090 ...    Off |   00000000:02:00.0 Off |
| N/A   56C    P8             12W /  150W |     474MiB /  24463MiB |     11%

Processes:
|    0   N/A  N/A         2149226      G   Hyprland                   6MiB |
|    0   N/A  N/A         2159510      G   /usr/bin/kitty           113MiB |
|    0   N/A  N/A         2164275      G   /usr/lib/firefox/firefox 275MiB |

Secondary Issue: Orphaned Containers

docker ps
Output
CONTAINER ID   IMAGE                              CREATED       STATUS
b4adb3ddcb5b   yuzutech/kroki:latest              8 hours ago   Up 8 hours
0ec14b4c2b92   yuzutech/kroki-mermaid:latest      8 hours ago   Up 8 hours
2fd5e9536c31   yuzutech/kroki-bpmn:latest         8 hours ago   Up 8 hours
1bdff3b2f82b   yuzutech/kroki-excalidraw:latest   8 hours ago   Up 8 hours

Findings

  1. Primary: Hyprland compositor is running on NVIDIA RTX 5090 instead of Intel iGPU

  2. Secondary: All Wayland clients (kitty, Firefox) inherit GPU from compositor

  3. Tertiary: Kroki containers running for 8 hours consuming additional resources

  4. Root cause: No WLR_DRM_DEVICES environment variable set to specify Intel GPU

Root Cause

Technical explanation: Hyprland compositor defaults to the most powerful GPU (RTX 5090) when no explicit device is specified via WLR_DRM_DEVICES. All Wayland clients then render through the compositor’s GPU, causing constant dGPU utilization even for basic desktop tasks.

Why it happened:

  • Immediate cause: Hyprland using RTX 5090 for desktop composition

  • Contributing factors: Default GPU selection behavior in wlroots-based compositors

  • Systemic issues: No power profile configuration for laptop mode