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.
omarchy-chromium-bin - Registration response error message: DEPRECATED_ENDPOINT
Reported by opswole · filed Aug 15, 2025Closed upstream on 2026-07-18 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
Hi,
Ran omarchy-update this morning and something within the new chromium-bin is failing, I don't have time to delve at the minute but the stack is below:
Packages (2) omarchy-chromium-bin-139.0.7258.66-7 omarchy-chromium-bin-debug-139.0.7258.66-7
Total Installed Size: 349.72 MiB
:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring [----------------------------------------------------------------------------] 100%
(2/2) checking package integrity [----------------------------------------------------------------------------] 100%
(2/2) loading package files [----------------------------------------------------------------------------] 100%
(2/2) checking for file conflicts [----------------------------------------------------------------------------] 100%
(2/2) checking available disk space [----------------------------------------------------------------------------] 100%
:: Processing package changes...
(1/2) installing omarchy-chromium-bin [----------------------------------------------------------------------------] 100%
(2/2) installing omarchy-chromium-bin-debug [----------------------------------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating icon theme caches...
(3/3) Updating the desktop file MIME type cache...
[11564:11584:0815/101225.405745:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[11564:11584:0815/101253.736314:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[11564:11584:0815/101335.097989:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[11564:11584:0815/101457.268958:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[11564:11584:0815/101816.475547:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[11564:11584:0815/102419.982314:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINTAny pointers on this would be great. I asked in the discord but was quickly flushed out by new messages. Perils of popularity!
View raw text
Hi, Ran `omarchy-update` this morning and something within the new chromium-bin is failing, I don't have time to delve at the minute but the stack is below: ``` Packages (2) omarchy-chromium-bin-139.0.7258.66-7 omarchy-chromium-bin-debug-139.0.7258.66-7 Total Installed Size: 349.72 MiB :: Proceed with installation? [Y/n] (2/2) checking keys in keyring [----------------------------------------------------------------------------] 100% (2/2) checking package integrity [----------------------------------------------------------------------------] 100% (2/2) loading package files [----------------------------------------------------------------------------] 100% (2/2) checking for file conflicts [----------------------------------------------------------------------------] 100% (2/2) checking available disk space [----------------------------------------------------------------------------] 100% :: Processing package changes... (1/2) installing omarchy-chromium-bin [----------------------------------------------------------------------------] 100% (2/2) installing omarchy-chromium-bin-debug [----------------------------------------------------------------------------] 100% :: Running post-transaction hooks... (1/3) Arming ConditionNeedsUpdate... (2/3) Updating icon theme caches... (3/3) Updating the desktop file MIME type cache... [11564:11584:0815/101225.405745:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT [11564:11584:0815/101253.736314:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT [11564:11584:0815/101335.097989:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT [11564:11584:0815/101457.268958:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT [11564:11584:0815/101816.475547:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT [11564:11584:0815/102419.982314:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT ``` Any pointers on this would be great. I asked in the discord but was quickly flushed out by new messages. Perils of popularity!
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.