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.
Waybar invisible on newly installed Omarchy 3.1.1
Reported by joelsifres · filed Oct 22, 2025Closed upstream on 2025-10-24 by its own reporter joelsifres. GitHub close reason: completed. Closed by its own reporter — not by itself 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
AMD Ryzen 7 5800H, Omarchy 3.1.1 master
What's wrong?
I just installed Omarchy 3.1.1 (latest version on the website) on my 2020 Asus laptop and everything works flawlessly except for Waybar, which is invisible even though it takes space at the top part of the screen (which is an external monitor because the laptop one doesn't work).
I have not changed any of its config (in fact I've tried restoring the default config with no luck), toggling it using Super + Shift + Space gets rid of the space at the top, but still doesn't show it, manually starting it with waybar doesn't do anything, and neither does running pkill waybar && hyprctl dispatch exec waybar~ or pkill waybar && waybar &.
I've noticed, though, that running waybar it gets stuck when loading the CSS file (which I have not changed, again it's vanilla config) and throws an error saying Timeout was reached.
> [2025-10-22 09:29:15.783] [info] Using configuration file /home/user/.config/waybar/config.jsonc
[2025-10-22 09:29:15.790] [info] Discovered appearance 'dark'
[2025-10-22 09:29:15.824] [info] Using CSS file /home/user/.config/waybar/style.css
Failed to register: Timeout was reached
[2025-10-22 09:29:40.858] [info] Hyprland IPC starting
And here's a screenshot of how it looks:
<img width="3843" height="2163" alt="Image" src="https://github.com/user-attachments/assets/d25c8dfc-6c0f-4e81-a198-dba9a644b8ca" />
View raw text
### System details AMD Ryzen 7 5800H, Omarchy 3.1.1 master ### What's wrong? I just installed Omarchy 3.1.1 (latest version on the website) on my 2020 Asus laptop and everything works flawlessly except for Waybar, which is invisible even though it takes space at the top part of the screen (which is an external monitor because the laptop one doesn't work). I have not changed any of its config (in fact I've tried restoring the default config with no luck), toggling it using `Super + Shift + Space` gets rid of the space at the top, but still doesn't show it, manually starting it with waybar doesn't do anything, and neither does running `pkill waybar && hyprctl dispatch exec waybar~` or `pkill waybar && waybar &`. I've noticed, though, that running waybar it gets stuck when loading the CSS file (which I have not changed, again it's vanilla config) and throws an error saying Timeout was reached. > [2025-10-22 09:29:15.783] [info] Using configuration file /home/user/.config/waybar/config.jsonc [2025-10-22 09:29:15.790] [info] Discovered appearance 'dark' [2025-10-22 09:29:15.824] [info] Using CSS file /home/user/.config/waybar/style.css Failed to register: Timeout was reached [2025-10-22 09:29:40.858] [info] Hyprland IPC starting And here's a screenshot of how it looks: <img width="3843" height="2163" alt="Image" src="https://github.com/user-attachments/assets/d25c8dfc-6c0f-4e81-a198-dba9a644b8ca" />
- d25c8dfc-6c0f-4e81-a198-dba9a644b8ca
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.