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.
mpv needs 'gpu-context=wayland' for proper fullscreen support
Reported by EFrMG · filed Jan 9, 2026Closed upstream on 2026-02-01 by dhh. 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
System details
Intel Core i3-8130U; UHD Graphics 620; Omarchy 3.3.3
What's wrong?
Default mpv configuration
For mpv to render correctly on wayland while on fullscreen, one needs to add gpu-context=wayland to its config.
This happens because of mpv defaulting to a faulty way for the GPU to manage the image, which Wayland sets on it correctly while not on fullscreen.
Demonstration
I have here a visual demonstration of this, where one can appreciate the pastel colors on monkeytype being barely distinct from each other:
Without the config fix
<img width="1902" height="858" alt="Image" src="https://github.com/user-attachments/assets/76168ddb-36ad-4090-917b-85eacf4007c5" />
And with the fix applied
<img width="1900" height="899" alt="Image" src="https://github.com/user-attachments/assets/f4358791-28e0-4725-b257-0cd0daf8b721" />
The screenshots were taken at roughly the same frame, yet are not edited in any manner.
The image could seem washed away, so to speak.
How I intend to contribute
I have made the following changes expressed in a future PR.
- Created a config file with just that one line at
config/ - Added a unix-timestamped migration script at
migrations/that does: - Check if the file exists and copies it from
config/otherwise. - If incorrect lines setting the same property exist, deletes them.
- If the line is not there then, checks if to add a newline and adds the simple line in question.
View raw text
### System details Intel Core i3-8130U; UHD Graphics 620; Omarchy 3.3.3 ### What's wrong? # Default mpv configuration For mpv to render correctly on wayland while on fullscreen, one needs to add `gpu-context=wayland` to its config. This happens because of mpv defaulting to a faulty way for the GPU to manage the image, which Wayland sets on it correctly while **not** on fullscreen. ## Demonstration I have here a visual demonstration of this, where one can appreciate the pastel colors on monkeytype being barely distinct from each other: ### Without the config fix <img width="1902" height="858" alt="Image" src="https://github.com/user-attachments/assets/76168ddb-36ad-4090-917b-85eacf4007c5" /> ### And with the fix applied <img width="1900" height="899" alt="Image" src="https://github.com/user-attachments/assets/f4358791-28e0-4725-b257-0cd0daf8b721" /> The screenshots were taken at roughly the same frame, yet are not edited in any manner. The image could seem _washed away_, so to speak. ## How I intend to contribute I have made the following changes expressed in a future PR. - Created a config file with just that one line at `config/` - Added a unix-timestamped migration script at `migrations/` that does: - Check if the file exists and copies it from `config/` otherwise. - If incorrect lines setting the same property exist, deletes them. - If the line is not there then, checks if to add a newline and adds the simple line in question.
- 76168ddb-36ad-4090-917b-85eacf4007c5
- f4358791-28e0-4725-b257-0cd0daf8b721
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.