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 GPU/Ozone errors after update to 3.2.3
Reported by GuilhermeNobre · filed Dec 16, 2025Closed upstream on 2026-02-27 by dhh. 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
Omarchy 3.2.3, 13th Gen Intel(R) Core, NVIDIA GeForce RTX 3050 6, Intel Raptor Lake-S UHD G
What's wrong?
After updating Omarchy to version 3.2.3, Chromium is failing to render correctly and spamming GPU/Ozone related errors in the terminal. The browser seems to have issues with SharedImageManager and OzoneImageBacking.
Steps to Reproduce
1. Update system to Omarchy 3.2.3.
2. Launch Chromium from the terminal.
3. Observe the output logs and browser behavior.
Logs
[5060:5060:1216/102938.234358:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:404] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
[5060:5060:1216/102938.242855:ERROR:ui/gl/angle_platform_impl.cc:42] ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
ERR: ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
[5060:5060:1216/102938.243001:ERROR:gpu/command_buffer/service/shared_image/ozone_image_backing.cc:316] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
...
[5018:5039:1216/103007.849483:ERROR:google_apis/gcm/engine/registration_request.cc:292] Registration response error message: QUOTA_EXCEEDEDView raw text
### System details Omarchy 3.2.3, 13th Gen Intel(R) Core, NVIDIA GeForce RTX 3050 6, Intel Raptor Lake-S UHD G ### What's wrong? After updating Omarchy to version 3.2.3, Chromium is failing to render correctly and spamming GPU/Ozone related errors in the terminal. The browser seems to have issues with `SharedImageManager` and `OzoneImageBacking`. **Steps to Reproduce** 1. Update system to Omarchy 3.2.3. 2. Launch Chromium from the terminal. 3. Observe the output logs and browser behavior. **Logs** ```text [5060:5060:1216/102938.234358:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:404] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking [5060:5060:1216/102938.242855:ERROR:ui/gl/angle_platform_impl.cc:42] ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009 ERR: ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009 [5060:5060:1216/102938.243001:ERROR:gpu/command_buffer/service/shared_image/ozone_image_backing.cc:316] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation ... [5018:5039:1216/103007.849483:ERROR:google_apis/gcm/engine/registration_request.cc:292] Registration response error message: QUOTA_EXCEEDED
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.