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

latest version of chromium crashes the machine when hardware acceleration is enabled

Reported by ferrao · filed Oct 29, 2025Closed upstream on 2026-07-18. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

latest version of chromium crashes the machine when hardware acceleration is enabledrevision 1 · captured 2026-10-04 11:42 UTC via poll

System details

Thinkpad Z13, CPU AMD Ryzen 7 PRO 6850U, GPU AMD Radeon 680M, Omarchy 3.1.4, kernel 6.17.5-arch1-1
Chromium 141.0.7390.122

What's wrong?

This is probably an upstream bug, but I still think it might be useful to track it here, feel free to close if you think otherwise.

With one of the latest updates executed via the Update/Omarchy menu, everytime I open a Google Meet Chromium will crash and bring the whole machine to a halt, the only option to recover from this is to perform a hard reset by holding the power button for a few seconds and rebooting again.

If i run chromium with --disable-gpu this does not happen.
If I install and run Google Chrome for the AUR, this does not happen.

I have attached the report created by chrome://gpu when hardware accelaration is enabled and disabled.

about-gpu-enabled-2025-10-29T11-57-32-857Z.txt
about-gpu-disabled-2025-10-29T11-55-47-173Z.txt

View raw text
### System details

Thinkpad Z13, CPU AMD Ryzen 7 PRO 6850U, GPU AMD Radeon 680M, Omarchy 3.1.4, kernel 6.17.5-arch1-1
Chromium  141.0.7390.122

### What's wrong?

This is probably an upstream bug, but I still think it might be useful to track it here, feel free to close if you think otherwise.

With one of the latest updates executed via the Update/Omarchy menu, everytime I open a Google Meet Chromium will crash and bring the whole machine to a halt, the only option to recover from this is to perform a hard reset by holding the power button for a few seconds and rebooting again.

If i run chromium with `--disable-gpu` this does not happen.
If I install and run Google Chrome for the AUR, this does not happen.

I have attached the report created by `chrome://gpu` when hardware accelaration is enabled and disabled.

[about-gpu-enabled-2025-10-29T11-57-32-857Z.txt](https://github.com/user-attachments/files/23209438/about-gpu-enabled-2025-10-29T11-57-32-857Z.txt)
[about-gpu-disabled-2025-10-29T11-55-47-173Z.txt](https://github.com/user-attachments/files/23209439/about-gpu-disabled-2025-10-29T11-55-47-173Z.txt)
  • about-gpu-enabled-2025-10-29T11-57-32-857Z.txt
  • about-gpu-disabled-2025-10-29T11-55-47-173Z.txt

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.