Proof Portal

Sign in
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-5110GitHub issuePublicReceived

LazyVim fails to start: catppuccin theme references removed colorscheme 'catppuccin-nvim'

Reported by Lazk3r · filed Sep 21, 2026Closed upstream on 2026-09-23 by the merge of PR #12864 (closed by bjarneo). GitHub close reason: completed.

Open at source
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

LazyVim fails to start: catppuccin theme references removed colorscheme 'catppuccin-nvim'revision 1 · captured 2026-10-04 12:10 UTC via poll

What happened

After updating Omarchy from a previous version to 4.0.4-1 ("Quattro"), Neovim (LazyVim) fails to start with the stock catppuccin theme active:

Error in command line:
Could not load your colorscheme

...local/share/nvim/lazy/LazyVim/lua/lazyvim/config/init.lua:253: Vim:E185: Cannot find color scheme 'catppuccin-nvim'

Root cause

/usr/share/omarchy/themes/catppuccin/neovim.lua sets:

{
  "LazyVim/LazyVim",
  opts = {
    colorscheme = "catppuccin-nvim",
  },
},

The currently pinned catppuccin/nvim plugin (commit 8c4125e3c746976ba025dc5d908fa22c6aa09486, 2025-10-25) no longer ships a colorscheme named catppuccin-nvim. Its colors/ directory only contains:

catppuccin.vim
catppuccin-latte.vim
catppuccin-frappe.vim
catppuccin-macchiato.vim
catppuccin-mocha.vim

For comparison, the sibling stock theme catppuccin-latte correctly uses the flavour-qualified name catppuccin-latte (which does exist), so the base catppuccin (mocha) theme should presumably use catppuccin-mocha instead of the stale catppuccin-nvim.

Steps to reproduce

  1. On a fresh/updated Omarchy 4.0.4-1 install, set the catppuccin theme: omarchy theme set catppuccin
  2. Launch nvim
  3. LazyVim throws E185: Cannot find color scheme 'catppuccin-nvim' on every startup

Expected

Neovim starts cleanly with the Catppuccin (mocha) colorscheme applied, as it did before the update.

Workaround applied locally

User-level overlay at ~/.config/omarchy/themes/catppuccin/neovim.lua changing colorscheme to catppuccin-mocha, then omarchy theme set catppuccin to re-stage it. This survives omarchy update since it lives outside /usr/share/omarchy, but the stock template should be fixed upstream.

System details

  • Omarchy version: 4.0.4-1
  • Kernel: Linux t480s 7.2.5-3-omarchy #1 SMP PREEMPT_DYNAMIC Mon, 14 Sep 2026 19:55:01 +0000 x86_64 GNU/Linux
  • CPU: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
  • GPU: Intel Corporation Kaby Lake-R GT2 [UHD Graphics 620] (rev 07)
  • Neovim: NVIM v0.12.5
  • LazyVim commit: d72127eb936f7f05d88d4fc316bc7e89080d69d8 (2025-10-26)
  • catppuccin/nvim commit: 8c4125e3c746976ba025dc5d908fa22c6aa09486 (2025-10-25)

(Note: omarchy debug --no-sudo --print is not available as a command on this Omarchy build, so no debug log/URL is attached.)

View raw text
## What happened

After updating Omarchy from a previous version to 4.0.4-1 ("Quattro"), Neovim (LazyVim) fails to start with the stock `catppuccin` theme active:

```
Error in command line:
Could not load your colorscheme

...local/share/nvim/lazy/LazyVim/lua/lazyvim/config/init.lua:253: Vim:E185: Cannot find color scheme 'catppuccin-nvim'
```

## Root cause

`/usr/share/omarchy/themes/catppuccin/neovim.lua` sets:

```lua
{
  "LazyVim/LazyVim",
  opts = {
    colorscheme = "catppuccin-nvim",
  },
},
```

The currently pinned `catppuccin/nvim` plugin (commit `8c4125e3c746976ba025dc5d908fa22c6aa09486`, 2025-10-25) no longer ships a colorscheme named `catppuccin-nvim`. Its `colors/` directory only contains:

```
catppuccin.vim
catppuccin-latte.vim
catppuccin-frappe.vim
catppuccin-macchiato.vim
catppuccin-mocha.vim
```

For comparison, the sibling stock theme `catppuccin-latte` correctly uses the flavour-qualified name `catppuccin-latte` (which does exist), so the base `catppuccin` (mocha) theme should presumably use `catppuccin-mocha` instead of the stale `catppuccin-nvim`.

## Steps to reproduce

1. On a fresh/updated Omarchy 4.0.4-1 install, set the `catppuccin` theme: `omarchy theme set catppuccin`
2. Launch `nvim`
3. LazyVim throws `E185: Cannot find color scheme 'catppuccin-nvim'` on every startup

## Expected

Neovim starts cleanly with the Catppuccin (mocha) colorscheme applied, as it did before the update.

## Workaround applied locally

User-level overlay at `~/.config/omarchy/themes/catppuccin/neovim.lua` changing `colorscheme` to `catppuccin-mocha`, then `omarchy theme set catppuccin` to re-stage it. This survives `omarchy update` since it lives outside `/usr/share/omarchy`, but the stock template should be fixed upstream.

## System details

- Omarchy version: 4.0.4-1
- Kernel: `Linux t480s 7.2.5-3-omarchy #1 SMP PREEMPT_DYNAMIC Mon, 14 Sep 2026 19:55:01 +0000 x86_64 GNU/Linux`
- CPU: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
- GPU: Intel Corporation Kaby Lake-R GT2 [UHD Graphics 620] (rev 07)
- Neovim: NVIM v0.12.5
- LazyVim commit: `d72127eb936f7f05d88d4fc316bc7e89080d69d8` (2025-10-26)
- catppuccin/nvim commit: `8c4125e3c746976ba025dc5d908fa22c6aa09486` (2025-10-25)

(Note: `omarchy debug --no-sudo --print` is not available as a command on this Omarchy build, so no debug log/URL is attached.)

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.