Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Laggy external monitor on a laptop
Reported by geass94 · filed Oct 19, 2025Closed upstream on 2026-07-18. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
What do you need?
<img width="733" height="267" alt="Image" src="https://github.com/user-attachments/assets/7ae0a6eb-0fe7-4435-aec4-fb3e978ce274" />
I do have 4k external monitor hooked up to my laptop. All animations even cursor movement is very laggy, feels 30Hz. I almost never use laptop monitor. So gaving controls in Setup -> Config would be nice to have controls for iGPU and dGPU priorities.
I ended up with solution like this.
Created symlinks for igpu and dgpu like so
SYMLINK_NAME="intel-igpu"
RULE_PATH="/etc/udev/rules.d/intel-igpu-dev-path.rules"
INTEL_IGPU_ID=$(lspci -d ::03xx | grep 'Intel' | cut -f1 -d' ')
sudo tee "$RULE_PATH" > /dev/null <<EOF
KERNEL=="card*", \
KERNELS=="$INTEL_IGPU_ID", \
SUBSYSTEM=="drm", \
SUBSYSTEMS=="pci", \
SYMLINK+="dri/$SYMLINK_NAME"
EOFand for nvidia
SYMLINK_NAME="nvidia-gpu"
RULE_PATH="/etc/udev/rules.d/nvidia-gpu-dev-path.rules"
NVIDIA_GPU_ID=$(lspci -d ::03xx | grep -i 'NVIDIA' | cut -f1 -d' ')
sudo tee "$RULE_PATH" > /dev/null <<EOF
KERNEL=="card*", \
KERNELS=="$NVIDIA_GPU_ID", \
SUBSYSTEM=="drm", \
SUBSYSTEMS=="pci", \
SYMLINK+="dri/$SYMLINK_NAME"
EOFin terminal
sudo udevadm control --reload-rules
sudo udevadm triggerthen in hyprland.coonf added line like so
env = AQ_DRM_DEVICES,/dev/dri/nvidia-gpu:/dev/dri/intel-igpu
Now system uses dGPU instead of iGPU and everything works perfectly fine, full 4k resolution with 100Hz (my monitors max) refresh rate on external monitor.
View raw text
### What do you need? <img width="733" height="267" alt="Image" src="https://github.com/user-attachments/assets/7ae0a6eb-0fe7-4435-aec4-fb3e978ce274" /> I do have 4k external monitor hooked up to my laptop. All animations even cursor movement is very laggy, feels 30Hz. I almost never use laptop monitor. So gaving controls in Setup -> Config would be nice to have controls for iGPU and dGPU priorities. I ended up with solution like this. Created symlinks for igpu and dgpu like so ``` SYMLINK_NAME="intel-igpu" RULE_PATH="/etc/udev/rules.d/intel-igpu-dev-path.rules" INTEL_IGPU_ID=$(lspci -d ::03xx | grep 'Intel' | cut -f1 -d' ') sudo tee "$RULE_PATH" > /dev/null <<EOF KERNEL=="card*", \ KERNELS=="$INTEL_IGPU_ID", \ SUBSYSTEM=="drm", \ SUBSYSTEMS=="pci", \ SYMLINK+="dri/$SYMLINK_NAME" EOF ``` and for nvidia ``` SYMLINK_NAME="nvidia-gpu" RULE_PATH="/etc/udev/rules.d/nvidia-gpu-dev-path.rules" NVIDIA_GPU_ID=$(lspci -d ::03xx | grep -i 'NVIDIA' | cut -f1 -d' ') sudo tee "$RULE_PATH" > /dev/null <<EOF KERNEL=="card*", \ KERNELS=="$NVIDIA_GPU_ID", \ SUBSYSTEM=="drm", \ SUBSYSTEMS=="pci", \ SYMLINK+="dri/$SYMLINK_NAME" EOF ``` in terminal ``` sudo udevadm control --reload-rules sudo udevadm trigger ``` then in hyprland.coonf added line like so `env = AQ_DRM_DEVICES,/dev/dri/nvidia-gpu:/dev/dri/intel-igpu` Now system uses dGPU instead of iGPU and everything works perfectly fine, full 4k resolution with 100Hz (my monitors max) refresh rate on external monitor.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.