Proof Portal

Sign in
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-1935GitHub issuePublicDecided· Out of scope

Hyprland Crash When Toggling Float on a Pinned Window Stranded by Cross-Monitor Workspace Move (Dual Monitor)

Reported by scadoshi · filed May 19, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Hyprland Crash When Toggling Float on a Pinned Window Stranded by Cross-Monitor Workspace Move (Dual Monitor)revision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Omarchy 3.8.1, Hyprland 0.54.3 (Wayland), Linux 7.0.3-arch1-2, Intel Core Ultra 7 155H, NVIDIA RTX 500 Ada + Intel Arc Graphics, ThinkPad P14s Gen 5, 62 GiB RAM, 3 displays (2x 1920x1080 external + 3072x1920 built-in)

What's wrong?

Hyprland Crash When Toggling Float on a Pinned Window Stranded by Cross-Monitor Workspace Move (Dual Monitor)

Environment

  • Two monitors required to reproduce

System Details

  • OS: Omarchy 3.8.1
  • Branch: master
  • Channel: stable
  • Kernel: Linux 7.0.3-arch1-2
  • WM: Hyprland 0.54.3 (Wayland)
  • Terminal: ghostty 1.3.1-arch2
  • Shell/Font: JetBrainsMono Nerd Font (9pt)
  • Theme: Gruvbox
  • PC: Lenovo ThinkPad P14s Gen 5 (21G2002BUS)
  • CPU: Intel Core Ultra 7 155H
  • GPU: NVIDIA RTX 500 Ada Generation Laptop GPU / Intel Arc Graphics @ 2.25 GHz
  • Displays:
  • 1920x1080 @ 75 Hz, 32" (External)
  • 1920x1080 @ 75 Hz, 32" (External)
  • 3072x1920 @ 2x, 60 Hz, 15" (Built-in)
  • RAM: 62.30 GiB
  • Disk: 1.82 TiB btrfs
  • Packages: 992 (pacman)
  • Uptime at crash: ~22 hours

Summary

Hyprland crashes immediately when toggling float on a floating/pinned window that was left behind after its workspace was moved between monitors and back.

Steps to Reproduce

  1. Focus a window and press Super + O to toggle float and pin it.
  2. Press Super + Alt + Shift + Arrow to move the current workspace to the other monitor.
  3. Move the workspace back to the original monitor with Super + Alt + Shift + Arrow in the opposite direction.
  4. Observe: the pinned/floating window did not travel with the workspace (it should have, or at least remain in a consistent state).
  5. Click the floating window to focus it.
  6. Press Super + O to toggle float off.

Expected

The window toggles back to tiled (or floats correctly) without crashing.

Actual

Hyprland crashes immediately on the float toggle in step 6.

Notes

  • Reproducible every time with the above sequence.
  • The floating/pinned window appears to end up in an inconsistent state after the workspace is shuffled between monitors, and toggling float on it is what triggers the crash.
View raw text
### System details

Omarchy 3.8.1, Hyprland 0.54.3 (Wayland), Linux 7.0.3-arch1-2, Intel Core Ultra 7 155H, NVIDIA RTX   500 Ada + Intel Arc Graphics, ThinkPad P14s Gen 5, 62 GiB RAM, 3 displays (2x 1920x1080 external +   3072x1920 built-in)

### What's wrong?

# Hyprland Crash When Toggling Float on a Pinned Window Stranded by Cross-Monitor Workspace Move (Dual Monitor)

## Environment
- Two monitors required to reproduce

### System Details
- **OS:** Omarchy 3.8.1
- **Branch:** master
- **Channel:** stable
- **Kernel:** Linux 7.0.3-arch1-2
- **WM:** Hyprland 0.54.3 (Wayland)
- **Terminal:** ghostty 1.3.1-arch2
- **Shell/Font:** JetBrainsMono Nerd Font (9pt)
- **Theme:** Gruvbox
- **PC:** Lenovo ThinkPad P14s Gen 5 (21G2002BUS)
- **CPU:** Intel Core Ultra 7 155H
- **GPU:** NVIDIA RTX 500 Ada Generation Laptop GPU / Intel Arc Graphics @ 2.25 GHz
- **Displays:**
  - 1920x1080 @ 75 Hz, 32" (External)
  - 1920x1080 @ 75 Hz, 32" (External)
  - 3072x1920 @ 2x, 60 Hz, 15" (Built-in)
- **RAM:** 62.30 GiB
- **Disk:** 1.82 TiB btrfs
- **Packages:** 992 (pacman)
- **Uptime at crash:** ~22 hours

## Summary
Hyprland crashes immediately when toggling float on a floating/pinned window that was left behind after its workspace was moved between monitors and back.

## Steps to Reproduce
1. Focus a window and press `Super + O` to toggle float and pin it.
2. Press `Super + Alt + Shift + Arrow` to move the current workspace to the other monitor.
3. Move the workspace back to the original monitor with `Super + Alt + Shift + Arrow` in the opposite direction.
4. Observe: the pinned/floating window did **not** travel with the workspace (it should have, or at least remain in a consistent state).
5. Click the floating window to focus it.
6. Press `Super + O` to toggle float off.

## Expected
The window toggles back to tiled (or floats correctly) without crashing.

## Actual
Hyprland crashes immediately on the float toggle in step 6.

## Notes
- Reproducible every time with the above sequence.
- The floating/pinned window appears to end up in an inconsistent state after the workspace is shuffled between monitors, and toggling float on it is what triggers the crash.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 03:48 UTC