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

sudo pacman -U /var/cache/pacman/pkg/omarchy-chromium-141.0.7390.54-1002-x86_64.pkg.tar.zst

/etc/pacman.conf
IgnorePkg = omarchy-chromium

View commit history:
flatpak remote-info --log flathub com.brave.Browser

Downgrade to older commit:
sudo flatpak update --commit=6ab4e1add8dd29f7a94fe515e77e475f5145718b72314629a7900c0c68292e08 com.brave.Browser

Prevent auto-updates:
sudo flatpak mask com.brave.Browser

### System details

i5-1335U, Intel Iris Xe, Omarchy v3.0.2

### What's wrong?

**Started after upgrading to:**
omarchy-chromium 141.0.7390.76-2 (2025-10-12)

**What happens**
After updating Chromium, moving Chromium window between monitors causes it to crash and sometimes triggers a Hyprland restart.

**Temporary workaround I found**
Downgrading these packages resolves the issue:
```
sudo pacman -U /var/cache/pacman/pkg/omarchy-chromium-141.0.7390.54-1002-x86_64.pkg.tar.zst
```

**To prevent auto-upgrade until fix arrives**
```
/etc/pacman.conf
IgnorePkg = omarchy-chromium
```
**Do the same for Brave installed via Flatpak**
```
View commit history:
flatpak remote-info --log flathub com.brave.Browser

Downgrade to older commit:
sudo flatpak update --commit=6ab4e1add8dd29f7a94fe515e77e475f5145718b72314629a7900c0c68292e08 com.brave.Browser

Prevent auto-updates:
sudo flatpak mask com.brave.Browser
```


Now dragging or moving chromium or brave window doesn't cause a 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.

No decision has been recorded yet.