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-3163GitHub issuePublicReceived

Chrome crashes when moving tile between monitors on Hyprland

Reported by Tatuck · filed Oct 3, 2025Closed upstream on 2025-10-04 by its own reporter Tatuck. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Open at source
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

Chrome crashes when moving tile between monitors on Hyprlandrevision 1 · captured 2026-10-04 11:35 UTC via poll

System details

AMD Ryzen 7 7840HS, NVIDIA GeForce RTX 4060 Max-Q, AMD Radeon 780M

What's wrong?

Hello.
When running Google Chrome with Wayland (--ozone-platform=wayland) under Omarchy (Hyprland), Chrome crashes if the window is moved from one monitor to another.
The following error appears in the terminal:

~ ❯ google-chrome-stable --ozone-platform=wayland
[25566:25566:1003/120242.562772:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[25566:25566:1003/120242.562831:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[25566:25566:1003/120243.276944:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[25566:25566:1003/120244.619696:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland: wl_display#1: error 0: invalid object 63

[1003/120244.631334:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[1003/120244.631782:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Trace/breakpoint trap      (core dumped) google-chrome-stable --ozone-platform=wayland

I was able to do this without having to change anything, but now I am receiving that error. Could it be because of the update? (v3.0.2)

Steps to reproduce:

  1. Launch Chrome with Wayland backend: google-chrome-stable --ozone-platform=wayland
  2. Move the Chrome window from one monitor to another using SUPER + SHIFT + 2
  3. Chrome crashes immediately with the above error.

Workarounds tried:

  1. Running with --ozone-platform=x11 works, but the scaling is broken (window contents appear oversized). The scaling can be fixed using --force-device-scale-factor=1.
  2. Updating Chrome and Hyprland didn’t resolve the issue.

I know that running Chrome with --ozone-platform=x11 --force-device-scale-factor=1 works as a workaround, but I’d like to understand why I didn’t need these flags before to move windows between monitors without crashing.

System info:

  • OS: Omarchy v3.0.2
  • Linux 6.16.10-arch1-1
  • Hyprland 0.51.1 (Wayland)
  • Google Chrome version: Google Chrome 141.0.7390.54

Thank you.

View raw text
### System details

AMD Ryzen 7 7840HS, NVIDIA GeForce RTX 4060 Max-Q, AMD Radeon 780M

### What's wrong?

Hello.
When running Google Chrome with Wayland (--ozone-platform=wayland) under Omarchy (Hyprland), Chrome crashes if the window is moved from one monitor to another.
The following error appears in the terminal:
```
~ ❯ google-chrome-stable --ozone-platform=wayland
[25566:25566:1003/120242.562772:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[25566:25566:1003/120242.562831:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[25566:25566:1003/120243.276944:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[25566:25566:1003/120244.619696:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland: wl_display#1: error 0: invalid object 63

[1003/120244.631334:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[1003/120244.631782:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Trace/breakpoint trap      (core dumped) google-chrome-stable --ozone-platform=wayland
```
I was able to do this without having to change anything, but now I am receiving that error. Could it be because of the update? (v3.0.2)

### Steps to reproduce:
1. Launch Chrome with Wayland backend: `google-chrome-stable --ozone-platform=wayland`
2. Move the Chrome window from one monitor to another using `SUPER + SHIFT + 2`
3. Chrome crashes immediately with the above error.

### Workarounds tried:
1. Running with `--ozone-platform=x11` works, but the scaling is broken (window contents appear oversized). The scaling can be fixed using `--force-device-scale-factor=1`.
2. Updating Chrome and Hyprland didn’t resolve the issue.

I know that running Chrome with `--ozone-platform=x11 --force-device-scale-factor=1` works as a workaround, but I’d like to understand why I didn’t need these flags before to move windows between monitors without crashing.

### System info:
- OS: Omarchy v3.0.2
- Linux 6.16.10-arch1-1
- Hyprland 0.51.1 (Wayland)
- Google Chrome version: Google Chrome 141.0.7390.54

Thank you.

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.