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.
Manual install fails, Conflict between ghostty and ncurses 6.6-1
Reported by SerrpentDagger · filed Feb 25, 2026Closed upstream on 2026-02-26 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not 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
virt-manager, Arch 2026.02.01 (latest), manual install on 2026.02.25
What's wrong?
Description
Manual installation fails from the latest Arch iso with the following error:
error: failed to commit transaction (conflicting files)
ghostty-terminfo: /usr/share/terminfo/g/ghostty exists in filesystem (owned by ncurses)
Errors occurred, no packages were upgraded.
...
Failed script: /home/user/local/share/omarchy/install/packaging/base.shContext
It seems this error happens when we try to install ghostty (I get the same error by attempting to first install ghostty directly in the Arch tty).
Discussions on other forums here and here suggest a conflict between ncurses 6.6-1 and ghostty, revolving around the /usr/share/terminfo/g/ghostty file.
Indeed if I check an older VM which installed correctly, it's running ncurses 6.5-4, while the new Arch iso ended up with ncurses 6.6-1.
Current workaround
As the linked forums suggest, you can get around the problem by removing the problematic file:
sudo rm /usr/share/terminfo/g/ghosttyI was able to continue with the install as expected after doing so, I'm just not quite sure if there are any side effects to the above removal.
View raw text
### System details virt-manager, Arch 2026.02.01 (latest), manual install on 2026.02.25 ### What's wrong? ## Description Manual installation fails from the latest Arch iso with the following error: ``` error: failed to commit transaction (conflicting files) ghostty-terminfo: /usr/share/terminfo/g/ghostty exists in filesystem (owned by ncurses) Errors occurred, no packages were upgraded. ... Failed script: /home/user/local/share/omarchy/install/packaging/base.sh ``` ## Context It seems this error happens when we try to install ghostty (I get the same error by attempting to first install ghostty directly in the Arch tty). Discussions on other forums [here](https://discuss.cachyos.org/t/ncurses-vs-ghostty-terminfo/23147) and [here](https://forum.endeavouros.com/t/ghostty-issue-with-ncurses/78173) suggest a conflict between ncurses 6.6-1 and ghostty, revolving around the `/usr/share/terminfo/g/ghostty` file. Indeed if I check an older VM which installed correctly, it's running ncurses 6.5-4, while the new Arch iso ended up with ncurses 6.6-1. ## Current workaround As the linked forums suggest, you can get around the problem by removing the problematic file: ``` sudo rm /usr/share/terminfo/g/ghostty ``` I was able to continue with the install as expected after doing so, I'm just not quite sure if there are any side effects to the above removal.
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.