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.
Screen recording not saved
Reported by Shankar-1212 · filed Oct 20, 2025Closed upstream on 2025-10-25 by ryanrhughes. 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
- PC: HP Pavilion Gaming Laptop 15-dk1xxx - CPU: Intel(R) Core(TM) i5-10300H (8) @ 4.50 GHz - GPU: NVIDIA GeForce GTX 1650 Mobile / Max-Q [Discrete], Intel UHD Graphics [Integrated] - Display: 1920x1080 @ 144 Hz, 15" - RAM: 15.39 GiB (5.67 GiB used) - Storage: 474.92 GiB (38.05 GiB used) - btrfs - OS: Omarchy 3.1.1 - Kernel: Linux 6.17.3-arch2-1 - Compositor: Hyprland 0.51.1 (Wayland) - Terminal: alacritty 0.16.1
What's wrong?
When using Alt + PrintScreen → select region, or omarchy-cmd-screenrecord to record a screen region:
- After stopping the recording via the Waybar stop button, the notification says the recording was saved in the Videos folder.
- No video file actually appears in the folder.
- Running omarchy-cmd-screenrecord in the terminal produces the following output:
~ ❯ omarchy-cmd-screenrecord
~ ❯ gsr info: gsr_kms_client_init: setting up connection to /usr/bin/gsr-kms-server
gsr info: gsr_kms_client_init: waiting for server to connect
kms server info: connecting to the client
gsr info: gsr_kms_client_init: server connected
gsr info: replacing file-backed unix domain socket with socketpair
kms server info: connected to the client
gsr info: using socketpair
gsr error: gsr_get_supported_video_codecs_vaapi: vaInitialize failed
gsr error: gsr_get_supported_video_codecs_vaapi: failed to query supported video codecs for device /dev/dri/renderD129
gsr error: failed to query for supported video codecs
Steps to reproduce:
1. Press Alt + PrintScreen in Omarchy.
2. Select a screen region.
3. Press Stop on the Waybar screen recording indicator.
4. Observe the notification says the video is saved, but no file appears.
5. Run omarchy-cmd-screenrecord to see VAAPI errors in terminal
<img width="1921" height="1081" alt="Image" src="https://github.com/user-attachments/assets/2ac3ca65-b25d-49ed-9187-c1defa6244b7" />
<img width="925" height="550" alt="Image" src="https://github.com/user-attachments/assets/7adcba9c-d1db-4f59-9e56-8e0a7f129c0a" />
View raw text
### System details - PC: HP Pavilion Gaming Laptop 15-dk1xxx - CPU: Intel(R) Core(TM) i5-10300H (8) @ 4.50 GHz - GPU: NVIDIA GeForce GTX 1650 Mobile / Max-Q [Discrete], Intel UHD Graphics [Integrated] - Display: 1920x1080 @ 144 Hz, 15" - RAM: 15.39 GiB (5.67 GiB used) - Storage: 474.92 GiB (38.05 GiB used) - btrfs - OS: Omarchy 3.1.1 - Kernel: Linux 6.17.3-arch2-1 - Compositor: Hyprland 0.51.1 (Wayland) - Terminal: alacritty 0.16.1 ### What's wrong? When using `Alt + PrintScreen` → select region, or `omarchy-cmd-screenrecord` to record a screen region: - After stopping the recording via the Waybar stop button, the notification says the recording was saved in the Videos folder. - No video file actually appears in the folder. - Running `omarchy-cmd-screenrecord` in the terminal produces the following output: ~ ❯ omarchy-cmd-screenrecord ~ ❯ gsr info: gsr_kms_client_init: setting up connection to /usr/bin/gsr-kms-server gsr info: gsr_kms_client_init: waiting for server to connect kms server info: connecting to the client gsr info: gsr_kms_client_init: server connected gsr info: replacing file-backed unix domain socket with socketpair kms server info: connected to the client gsr info: using socketpair gsr error: gsr_get_supported_video_codecs_vaapi: vaInitialize failed gsr error: gsr_get_supported_video_codecs_vaapi: failed to query supported video codecs for device /dev/dri/renderD129 gsr error: failed to query for supported video codecs **Steps to reproduce:** 1. Press `Alt + PrintScreen` in Omarchy. 2. Select a screen region. 3. Press Stop on the Waybar screen recording indicator. 4. Observe the notification says the video is saved, but no file appears. 5. Run `omarchy-cmd-screenrecord` to see VAAPI errors in terminal <img width="1921" height="1081" alt="Image" src="https://github.com/user-attachments/assets/2ac3ca65-b25d-49ed-9187-c1defa6244b7" /> <img width="925" height="550" alt="Image" src="https://github.com/user-attachments/assets/7adcba9c-d1db-4f59-9e56-8e0a7f129c0a" />
- 2ac3ca65-b25d-49ed-9187-c1defa6244b7
- 7adcba9c-d1db-4f59-9e56-8e0a7f129c0a
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.