Proof Portal

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

Installing zsh broke my install.

Reported by hsyed · filed Jul 13, 2025Closed upstream on 2025-07-14 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

Installing zsh broke my install.revision 1 · captured 2026-10-04 11:26 UTC via poll

Howdy, and thanks for making Omarchy!

What happened
1. Installed zsh (yay -S zsh) so I could use it only inside Ghostty.
2. Rebooted. Instead of Hyprland, I was dropped into a zsh TTY.
3. Assumption: installing zsh changed my login shell, so the exec Hyprland line in ~/.bash_profile was never sourced.

Assuming it is the login shell change, are there other ways of launching hyperland so its not tied to a particular shell ?


I'll have to do a clean install. I ended up bricking my install by uninstalling zsh 🤡 -- I assume it would revert the login shell to bash. I tried to fix this by reinstalling bash in rescue mode (boot flag systemd.unit=rescue.target) but it gave me this:

failed to execute /usr/bin/bash: Exec format error
failed to execute /bin/sh: Exec format error

I have no idea what caused this, I just did a yay -S bash (as root) 🤷‍♂️.

View raw text
Howdy, and thanks for making Omarchy!

What happened
1.	Installed zsh (yay -S zsh) so I could use it only inside Ghostty.
2.	Rebooted. Instead of Hyprland, I was dropped into a zsh TTY.
3.	Assumption: installing zsh changed my login shell, so the exec Hyprland line in ~/.bash_profile was never sourced.

Assuming it is the login shell change, are there other ways of launching hyperland so its not tied to a particular shell ? 

----

I'll have to do a clean install. I ended up bricking my install by uninstalling zsh 🤡 -- I assume it would revert the login shell to bash. I tried to fix this by reinstalling bash in rescue mode (boot flag `systemd.unit=rescue.target`) but it gave me this:

```
failed to execute /usr/bin/bash: Exec format error
failed to execute /bin/sh: Exec format error
```
I have no idea what caused this, I just did a `yay -S bash` (as root) 🤷‍♂️.

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.