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.
iMac12,2 (Mid 2011, Radeon HD 6770M + HD 3000): Chromium renders with artifacts on legacy radeon/no-Vulkan GPUs; fixed by --disable-gpu-compositing
Reported by spuder · filed Sep 29, 2026 · open at source
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
System details
iMac12,2 (27" Mid 2011), Intel i5-2500S, Intel HD 3000 (i915) + AMD Radeon HD 6770M (legacy radeon driver, no Vulkan), Omarchy 4.0.4, kernel 7.2.5-3-omarchy, Hyprland 0.56.2, Chromium 152.0.7977.82, Mesa 26.2.2
What's wrong?
With the default Omarchy chromium-flags.conf, Chromium shows rendering artifacts and glitches on this iMac. Neither GPU supports Vulkan: the HD 3000 is Gen6 and the Radeon uses the legacy radeon driver. journalctl shows no DRM/GPU errors from i915 or radeon, so the problem looks like it's in Chromium's GPU compositing path rather than the kernel driver.
Steps to reproduce
- Install Omarchy on an iMac12,2, which has HD 3000 + Radeon HD 6770M on
radeon. - Launch Chromium with the stock flags (
--ozone-platform=wayland, etc.). - Browse normally. Pages render with artifacts and glitching.
What I tried
| Flags | Result |
|---|---|
--use-angle=gl --disable-features=Vulkan,SkiaGraphite | Did not fix it |
--disable-gpu-compositing | Fixed |
Workaround:
echo '--disable-gpu-compositing' >> ~/.config/chromium-flags.confRelated
- #3603, now discussion #6274: Chromium hard-freezes on legacy Radeon HD 5xxx (TeraScale 2,
radeondriver). It's the same hardware class and was fixed by software rendering. It was converted to a discussion and has no fix yet. - #3581: Ghostty crashes on legacy GPUs. It was fixed by install-time legacy-GPU detection that falls back to Alacritty (PR #3711).
- #2800: disabling GPU acceleration also fixes Chromium flicker there, though on newer hardware.
- #13174:
--disable-gpu-compositingmakes things worse on Intel Iris Xe, so it should not become a global default.
Possible fix
Extend the legacy-GPU detection from #3711 so it also appends --disable-gpu-compositing to ~/.config/chromium-flags.conf. It would trigger when a display device is bound to radeon, or on Intel Gen6 and older. That keeps modern GPUs on the current defaults.
Other Vulkan consumers on this machine log fallbacks like the following, which confirms that no Vulkan path works here:
radv_physical_device.c: Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver (VK_ERROR_INCOMPATIBLE_DRIVER)View raw text
### System details iMac12,2 (27" Mid 2011), Intel i5-2500S, Intel HD 3000 (i915) + AMD Radeon HD 6770M (legacy `radeon` driver, no Vulkan), Omarchy 4.0.4, kernel 7.2.5-3-omarchy, Hyprland 0.56.2, Chromium 152.0.7977.82, Mesa 26.2.2 ### What's wrong? With the default Omarchy `chromium-flags.conf`, Chromium shows rendering artifacts and glitches on this iMac. Neither GPU supports Vulkan: the HD 3000 is Gen6 and the Radeon uses the legacy `radeon` driver. `journalctl` shows no DRM/GPU errors from `i915` or `radeon`, so the problem looks like it's in Chromium's GPU compositing path rather than the kernel driver. **Steps to reproduce** 1. Install Omarchy on an iMac12,2, which has HD 3000 + Radeon HD 6770M on `radeon`. 2. Launch Chromium with the stock flags (`--ozone-platform=wayland`, etc.). 3. Browse normally. Pages render with artifacts and glitching. **What I tried** | Flags | Result | |---|---| | `--use-angle=gl --disable-features=Vulkan,SkiaGraphite` | Did not fix it | | `--disable-gpu-compositing` | **Fixed** | Workaround: ``` echo '--disable-gpu-compositing' >> ~/.config/chromium-flags.conf ``` **Related** - #3603, now discussion #6274: Chromium hard-freezes on legacy Radeon HD 5xxx (TeraScale 2, `radeon` driver). It's the same hardware class and was fixed by software rendering. It was converted to a discussion and has no fix yet. - #3581: Ghostty crashes on legacy GPUs. It was fixed by install-time legacy-GPU detection that falls back to Alacritty (PR #3711). - #2800: disabling GPU acceleration also fixes Chromium flicker there, though on newer hardware. - #13174: `--disable-gpu-compositing` makes things *worse* on Intel Iris Xe, so it should not become a global default. **Possible fix** Extend the legacy-GPU detection from #3711 so it also appends `--disable-gpu-compositing` to `~/.config/chromium-flags.conf`. It would trigger when a display device is bound to `radeon`, or on Intel Gen6 and older. That keeps modern GPUs on the current defaults. Other Vulkan consumers on this machine log fallbacks like the following, which confirms that no Vulkan path works here: ``` radv_physical_device.c: Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver (VK_ERROR_INCOMPATIBLE_DRIVER) ```
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 20:11 UTC