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.
Changing default shell to `fish` causes black screen on boot on 3.1.x
Reported by lukehsiao · filed Oct 16, 2025Closed upstream on 2025-10-17 by its own reporter lukehsiao. 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
Thinkpad T480s, i7-8650U, Intel UHD 620, Omarch 3.1.0-RC
What's wrong?
I switched to the dev branch to test 3.1.0 features, and discovered that after entering my LUKS password, I would hang at a black screen (similar to the symptoms of #2307 #2469).
In order to get to the bottom of it, I installed fresh from offline 3.0.2 ISO, updated fully, then switch to the dev branch and updated fully again. Everything worked, indicating that it was definitely my customization, not something wrong with base omarchy.
One by one I applied my customizations, restarting the machine between each, until:
chsh -s /usr/bin/fishresulted in the hang.
Indeed, switching to a TTY and chsh -s /usr/bin/bash and restarting resolved it.
I'm not sure off the top of my head how to get better visibility on why that is the problem, but that is what I see. Happy to try more things if someone has pointers.
Fish as default has been working fine on 3.0.x.
I suppose this isn't unexpected, even Fish gives the warning:
Setting fish as your login shell may cause issues, such as an incorrect PATH. Some operating systems, including a number of Linux distributions, require the login shell to be Bourne-compatible and to read configuration from /etc/profile. fish may not be suitable as a login shell on these systems.
Consequently, this is arguably NOT A BUG. However, it still feels worth posting here in case this helps someone else.
View raw text
### System details Thinkpad T480s, i7-8650U, Intel UHD 620, Omarch 3.1.0-RC ### What's wrong? I switched to the dev branch to test 3.1.0 features, and discovered that after entering my LUKS password, I would hang at a black screen (similar to the symptoms of #2307 #2469). In order to get to the bottom of it, I installed fresh from offline 3.0.2 ISO, updated fully, then switch to the dev branch and updated fully again. Everything worked, indicating that it was definitely my customization, not something wrong with base omarchy. One by one I applied my customizations, restarting the machine between each, until: ``` chsh -s /usr/bin/fish ``` resulted in the hang. Indeed, switching to a TTY and `chsh -s /usr/bin/bash` and restarting resolved it. I'm not sure off the top of my head how to get better visibility on _why_ that is the problem, but that is what I see. Happy to try more things if someone has pointers. Fish as default has been working fine on 3.0.x. I suppose this isn't _unexpected_, even Fish gives the warning: > Setting fish as your login shell may cause issues, such as an incorrect [PATH](https://fishshell.com/docs/current/language.html#envvar-PATH). Some operating systems, including a number of Linux distributions, require the login shell to be Bourne-compatible and to read configuration from /etc/profile. fish may not be suitable as a login shell on these systems. Consequently, this is arguably NOT A BUG. However, it still feels worth posting here in case this helps someone else.
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.