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.
screenrecorder does not work for region
Reported by matheusgomes28 · filed Mar 1, 2026Closed upstream on 2026-07-18 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
NVIDIA RTX A500
What's wrong?
The screen recorder script does not work when a region is selected, the vanilla logs for omarchy-cmd-screenrecord are:
$ ./omarchy-cmd-screenrecord
gsr info: option '-w portal' was used without '-restore-portal-session yes'. The previous screencast session will be ignored
gsr info: gsr_capture_portal_setup_dbus: CreateSession
gsr info: gsr_capture_portal_setup_dbus: SelectSources
gsr info: gsr_capture_portal_setup_dbus: Start
gsr info: gsr_capture_portal_save_restore_token: saved restore token to cache (dd89fab2-d130-4651-a03a-60c5cceac92e)
gsr info: gsr_capture_portal_setup_dbus: OpenPipeWireRemote
gsr info: gsr_capture_portal_setup_dbus: desktop portal setup finished
gsr info: gsr_capture_portal_setup: setting up pipewire
gsr info: pipewire: server version: 1.4.10
gsr info: pipewire: library version: 1.4.10
gsr info: pipewire: header version: 1.4.10
gsr info: pipewire: stream 0x557003f75ff0 previous state: "unconnected", new state: "connecting" (error: none)
gsr info: gsr_capture_portal_setup: pipewire setup finished
gsr info: gsr_capture_portal_start: waiting for pipewire negotiation
gsr info: pipewire: stream 0x557003f75ff0 previous state: "connecting", new state: "paused" (error: none)
gsr info: pipewire: negotiated format:
gsr info: pipewire: Format: 12 (Spa:Enum:VideoFormat:BGRA)
gsr info: pipewire: Modifier: 0x0
gsr info: pipewire: Size: 713x587
gsr info: pipewire: Framerate: 0/1
gsr info: pipewire: negotiated format:
gsr info: pipewire: Format: 12 (Spa:Enum:VideoFormat:BGRA)
gsr info: pipewire: Modifier: 0x100000000000008
gsr info: pipewire: Size: 713x587
gsr info: pipewire: Framerate: 0/1
gsr info: pipewire: stream 0x557003f75ff0 previous state: "paused", new state: "streaming" (error: none)
gsr info: gsr_capture_portal_start: timed out waiting for pipewire negotiation (5 seconds)
gsr info: pipewire: stream 0x557003f75ff0 previous state: "streaming", new state: "paused" (error: none)
gsr info: pipewire: stream 0x557003f75ff0 previous state: "paused", new state: "unconnected" (error: none)
gsr error: gsr_capture_start failedAfter applying the suggestion (adding -restore-portal-session yes to the gpu-screen-record command), it does start recording after the second activation of the tool. However, the resulting video can be seen below:
https://github.com/user-attachments/assets/8cc2ff2e-2e0c-4e58-b64b-0a87e57e99cb
slurpseems to be returning the correct selected region.- I'm unsure that the dbus
portalselections are being respected, I seem to not be able to share screen regions on chromium as well.
View raw text
### System details NVIDIA RTX A500 ### What's wrong? The screen recorder script does not work when a region is selected, the vanilla logs for `omarchy-cmd-screenrecord` are: ``` $ ./omarchy-cmd-screenrecord gsr info: option '-w portal' was used without '-restore-portal-session yes'. The previous screencast session will be ignored gsr info: gsr_capture_portal_setup_dbus: CreateSession gsr info: gsr_capture_portal_setup_dbus: SelectSources gsr info: gsr_capture_portal_setup_dbus: Start gsr info: gsr_capture_portal_save_restore_token: saved restore token to cache (dd89fab2-d130-4651-a03a-60c5cceac92e) gsr info: gsr_capture_portal_setup_dbus: OpenPipeWireRemote gsr info: gsr_capture_portal_setup_dbus: desktop portal setup finished gsr info: gsr_capture_portal_setup: setting up pipewire gsr info: pipewire: server version: 1.4.10 gsr info: pipewire: library version: 1.4.10 gsr info: pipewire: header version: 1.4.10 gsr info: pipewire: stream 0x557003f75ff0 previous state: "unconnected", new state: "connecting" (error: none) gsr info: gsr_capture_portal_setup: pipewire setup finished gsr info: gsr_capture_portal_start: waiting for pipewire negotiation gsr info: pipewire: stream 0x557003f75ff0 previous state: "connecting", new state: "paused" (error: none) gsr info: pipewire: negotiated format: gsr info: pipewire: Format: 12 (Spa:Enum:VideoFormat:BGRA) gsr info: pipewire: Modifier: 0x0 gsr info: pipewire: Size: 713x587 gsr info: pipewire: Framerate: 0/1 gsr info: pipewire: negotiated format: gsr info: pipewire: Format: 12 (Spa:Enum:VideoFormat:BGRA) gsr info: pipewire: Modifier: 0x100000000000008 gsr info: pipewire: Size: 713x587 gsr info: pipewire: Framerate: 0/1 gsr info: pipewire: stream 0x557003f75ff0 previous state: "paused", new state: "streaming" (error: none) gsr info: gsr_capture_portal_start: timed out waiting for pipewire negotiation (5 seconds) gsr info: pipewire: stream 0x557003f75ff0 previous state: "streaming", new state: "paused" (error: none) gsr info: pipewire: stream 0x557003f75ff0 previous state: "paused", new state: "unconnected" (error: none) gsr error: gsr_capture_start failed ``` After applying the suggestion (adding `-restore-portal-session yes` to the `gpu-screen-record` command), it does start recording after the second activation of the tool. However, the resulting video can be seen below: https://github.com/user-attachments/assets/8cc2ff2e-2e0c-4e58-b64b-0a87e57e99cb + `slurp` seems to be returning the correct selected region. + I'm unsure that the dbus `portal` selections are being respected, I seem to not be able to share screen regions on chromium as well.
- 8cc2ff2e-2e0c-4e58-b64b-0a87e57e99cb
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.