Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Chromium Causes System Freeze/Hang on Legacy GPUs (ATI Radeon HD 5xxx)
Reported by yaroslavrick · filed Nov 24, 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.
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
System details
ATI Radeon HD 5xxx, Omarchy 3.2.0
What's wrong?
On older hardware utilizing legacy ATI/AMD graphics cards (specifically TeraScale 2 architecture using the radeon driver), launching Chromium results in a complete system freeze (hard lock) within a few seconds of startup.
The issue appears to be a conflict between the legacy open-source radeon driver, the Wayland compositor, and Chromium's default hardware acceleration.
Hardware Example
Device: Sony Vaio PCG-61212T (and similar laptops from ~2010)
GPU: ATI Mobility Radeon HD 5000 series
Driver: radeon (open source)
Environment: Wayland (Hyprland)
Diagnosis / Root Cause
The legacy radeon driver seems unable to handle modern hardware acceleration requests made by the Chromium engine under Wayland. This leads to a GPU hang that locks up the entire system, requiring a hard reboot.
I confirmed that switching Chromium to software rendering (CPU only) completely resolves the stability issue.
The Fix / Workaround
I successfully resolved the issue by forcing Chromium to disable GPU acceleration via its persistent configuration file. This is a cleaner solution than modifying .desktop files.
Steps to fix:
Create or edit the Chromium flags configuration file:
nano ~/.config/chromium-flags.confAdd the following line to the file:
--disable-gpuSave and launch Chromium. The browser now runs stable using software rendering.
Suggested Resolution
Since Omarchy targets a wide range of hardware, please consider:
- Documentation: Adding a note to the Wiki or documentation regarding legacy GPUs (Pre-GCN AMD) and Chromium-based browsers.
- Auto-configuration: Ideally, the installation script could detect if the system is running on the legacy radeon driver and automatically generate
~/.config/chromium-flags.confwith the--disable-gpuflag to prevent immediate system freezing for new users.
View raw text
### System details ATI Radeon HD 5xxx, Omarchy 3.2.0 ### What's wrong? On older hardware utilizing legacy ATI/AMD graphics cards (specifically TeraScale 2 architecture using the radeon driver), launching Chromium results in a complete system freeze (hard lock) within a few seconds of startup. The issue appears to be a conflict between the legacy open-source radeon driver, the Wayland compositor, and Chromium's default hardware acceleration. ## Hardware Example Device: Sony Vaio PCG-61212T (and similar laptops from ~2010) GPU: ATI Mobility Radeon HD 5000 series Driver: radeon (open source) Environment: Wayland (Hyprland) ## Diagnosis / Root Cause The legacy radeon driver seems unable to handle modern hardware acceleration requests made by the Chromium engine under Wayland. This leads to a GPU hang that locks up the entire system, requiring a hard reboot. I confirmed that switching Chromium to software rendering (CPU only) completely resolves the stability issue. ## The Fix / Workaround I successfully resolved the issue by forcing Chromium to disable GPU acceleration via its persistent configuration file. This is a cleaner solution than modifying .desktop files. ### Steps to fix: Create or edit the Chromium flags configuration file: ```bash nano ~/.config/chromium-flags.conf ``` Add the following line to the file: ```text --disable-gpu ``` Save and launch Chromium. The browser now runs stable using software rendering. ## Suggested Resolution Since Omarchy targets a wide range of hardware, please consider: - Documentation: Adding a note to the Wiki or documentation regarding legacy GPUs (Pre-GCN AMD) and Chromium-based browsers. - Auto-configuration: Ideally, the installation script could detect if the system is running on the legacy radeon driver and automatically generate `~/.config/chromium-flags.conf` with the `--disable-gpu` flag to prevent immediate system freezing for new users.
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.