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-4054GitHub issuePublicReceived

waybar crash after omarchy update (breaks ~/.config/waybar/style.css)

Reported by jason-curtis · filed Jan 20, 2026Closed upstream on 2026-02-01 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

waybar crash after omarchy update (breaks ~/.config/waybar/style.css)revision 1 · captured 2026-10-04 11:49 UTC via poll

System details

Omarchy 3.3.3

What's wrong?

After running omarchy update to 3.3.3, waybar fails to start and the top bar disappears. The issue is caused by the theme no longer providing a waybar.css file, while the default waybar configuration still tries to import it.

### Error

when attempting to run waybar:
[error] style.css:1:46 Failed to import: Error opening file /home/[me]/.config/omarchy/current/theme/waybar.css: No such file or directory

### Steps to recreate

  1. Use the hackerman theme (it appears this would affect other themes as well)
  2. Have waybar configured with the default Omarchy waybar setup that imports ~/.config/omarchy/current/theme/waybar.css
  3. Run omarchy update to 3.3.3
  4. Waybar crashes on startup because the theme file is missing

### Expected behavior

Waybar should continue working after an update, or the update process should handle theme structure changes gracefully.

### Workaround

Remove the @import "../omarchy/current/theme/waybar.css"; line in ~/.config/waybar/style.css

### Additional context

  • The hackerman theme directory contains: colors.toml, btop.theme, neovim.lua, etc., but no waybar.css
View raw text
### System details

Omarchy 3.3.3

### What's wrong?


  After running `omarchy update` to `3.3.3`, waybar fails to start and the top bar disappears. The issue is caused by the theme no longer providing a `waybar.css` file, while the default waybar configuration still tries to import it.

  ### Error

when attempting to run `waybar`:
  `[error] style.css:1:46 Failed to import: Error opening file /home/[me]/.config/omarchy/current/theme/waybar.css: No such file or directory`

  ### Steps to recreate

  1. Use the hackerman theme (it appears this would affect other themes as well)
  2. Have waybar configured with the default Omarchy waybar setup that imports `~/.config/omarchy/current/theme/waybar.css`
  3. Run `omarchy update` to `3.3.3`
  4. Waybar crashes on startup because the theme file is missing

  ### Expected behavior

  Waybar should continue working after an update, or the update process should handle theme structure changes gracefully.

  ### Workaround

  Remove the `@import "../omarchy/current/theme/waybar.css";` line in `~/.config/waybar/style.css` 

  ### Additional context

  - The hackerman theme directory contains: `colors.toml`, `btop.theme`, `neovim.lua`, etc., but no `waybar.css`

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.