Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4014GitHub issuePublicReceived

Screenshots and screen recordings are inverted on monitors with transform applied

Reported by rblalock · filed Jan 10, 2026Closed upstream on 2026-01-29 by ryanrhughes, as a duplicate of #4196 (R-4001). GitHub close reason: duplicate.

Received and recorded verbatim. Nothing has been checked yet.

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

Screenshots and screen recordings are inverted on monitors with transform appliedrevision 1 · captured 2026-10-04 11:49 UTC via poll

Description

When taking screenshots (omarchy-cmd-screenshot) or screen recordings (omarchy-cmd-screenrecord) on a monitor that has a transform applied (e.g., portrait mode rotation), the captured image/video is inverted/rotated incorrectly.

Environment

  • Omarchy version: 3.3.3
  • Hyprland version: 0.53.1
  • grim version: 1.5.0-2
  • gpu-screen-recorder version: r1257.640e377-1

Monitor Configuration

monitor=DP-3,[email protected],1296x470,1.6666667
monitor=HDMI-A-1,[email protected],0x0,1.666667
monitor=HDMI-A-1,transform,3

The HDMI-A-1 monitor has transform,3 (270° rotation) for portrait orientation.

Steps to Reproduce

  1. Configure a monitor with a transform (e.g., transform,3 for portrait mode)
  2. Focus on a window on that transformed monitor
  3. Take a screenshot with Ctrl+Super+4 or screen recording with Ctrl+Super+5
  4. The resulting image/video is rotated incorrectly (inverted)

Expected Behavior

Screenshots and screen recordings should appear with the correct orientation, matching what is displayed on screen.

Actual Behavior

The captured content is rotated/inverted because grim and gpu-screen-recorder capture the raw framebuffer before Hyprland applies the display transform.

Root Cause

Both grim and gpu-screen-recorder capture the framebuffer without accounting for Hyprland's display transform. The screenshot/screenrecord scripts would need to:

  1. Detect if the capture region is on a transformed monitor
  2. Apply the inverse rotation to the captured image/video

Potential Solutions

For screenshots (omarchy-cmd-screenshot)

Detect the monitor transform and pipe the grim output through ImageMagick to apply the inverse rotation:

# Example: for transform,3 (270°), apply -rotate 90 to correct
grim -g "$SELECTION" - | convert - -rotate 90 - | satty ...

For screen recordings (omarchy-cmd-screenrecord)

Use ffmpeg's -vf transpose filter via the -ffmpeg-opts flag in gpu-screen-recorder, or post-process the video.

Additional Context

This affects any multi-monitor setup where one or more monitors use portrait orientation via Hyprland's transform feature.

View raw text
## Description

When taking screenshots (`omarchy-cmd-screenshot`) or screen recordings (`omarchy-cmd-screenrecord`) on a monitor that has a `transform` applied (e.g., portrait mode rotation), the captured image/video is inverted/rotated incorrectly.

## Environment

- **Omarchy version:** 3.3.3
- **Hyprland version:** 0.53.1
- **grim version:** 1.5.0-2
- **gpu-screen-recorder version:** r1257.640e377-1

## Monitor Configuration

```
monitor=DP-3,[email protected],1296x470,1.6666667
monitor=HDMI-A-1,[email protected],0x0,1.666667
monitor=HDMI-A-1,transform,3
```

The HDMI-A-1 monitor has `transform,3` (270° rotation) for portrait orientation.

## Steps to Reproduce

1. Configure a monitor with a transform (e.g., `transform,3` for portrait mode)
2. Focus on a window on that transformed monitor
3. Take a screenshot with `Ctrl+Super+4` or screen recording with `Ctrl+Super+5`
4. The resulting image/video is rotated incorrectly (inverted)

## Expected Behavior

Screenshots and screen recordings should appear with the correct orientation, matching what is displayed on screen.

## Actual Behavior

The captured content is rotated/inverted because `grim` and `gpu-screen-recorder` capture the raw framebuffer before Hyprland applies the display transform.

## Root Cause

Both `grim` and `gpu-screen-recorder` capture the framebuffer without accounting for Hyprland's display transform. The screenshot/screenrecord scripts would need to:

1. Detect if the capture region is on a transformed monitor
2. Apply the inverse rotation to the captured image/video

## Potential Solutions

### For screenshots (`omarchy-cmd-screenshot`)
Detect the monitor transform and pipe the grim output through ImageMagick to apply the inverse rotation:

```bash
# Example: for transform,3 (270°), apply -rotate 90 to correct
grim -g "$SELECTION" - | convert - -rotate 90 - | satty ...
```

### For screen recordings (`omarchy-cmd-screenrecord`)
Use ffmpeg's `-vf transpose` filter via the `-ffmpeg-opts` flag in gpu-screen-recorder, or post-process the video.

## Additional Context

This affects any multi-monitor setup where one or more monitors use portrait orientation via Hyprland's transform feature.

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.