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.
Installation script fails to fetch AUR package due to connection error
Reported by PranavKumar9529desai · filed Aug 13, 2025Closed upstream on 2025-08-13 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
I encountered an issue while running the Omarchy installation script on a fresh Arch Linux setup. The script failed to download a package from the Arch User Repository (AUR), which prevented the installation from completing.
Steps to Reproduce:
Booted into a fresh Arch Linux installation.
Ran the Omarchy installation script (e.g., bash /usr/local/share/omarchy/install.sh).
The script began the installation process, but then failed when trying to fetch a package from the AUR.
Error Output:
'''
First Error Message:
fatal: unable to access 'https://aur.archlinux.org/python-terminaltextfects.git/': OpenSSL SSL_read: error:00000126:SSL routines::unexpected eof while reading
Second Error Message:
-> request failed: Get "https://aur.archlinux.org/rpc?v=5&type=info&arg[]python-terminaltextffects": dial tcp 95.216.194.15:443: i/o timeout
'''
Context & Analysis:
My local internet connection was confirmed to be stable and working (e.g., ping google.com was successful with 0% packet loss).
The issue appears to be an i/o timeout and unexpected eof when the script attempts a TLS handshake with aur.archlinux.org.
This suggests a potential issue with the AUR server itself or a network problem on their end, rather than a problem with the user's connection.
View raw text
I encountered an issue while running the Omarchy installation script on a fresh Arch Linux setup. The script failed to download a package from the Arch User Repository (AUR), which prevented the installation from completing. Steps to Reproduce: Booted into a fresh Arch Linux installation. Ran the Omarchy installation script (e.g., bash /usr/local/share/omarchy/install.sh). The script began the installation process, but then failed when trying to fetch a package from the AUR. Error Output: ''' First Error Message: fatal: unable to access 'https://aur.archlinux.org/python-terminaltextfects.git/': OpenSSL SSL_read: error:00000126:SSL routines::unexpected eof while reading Second Error Message: -> request failed: Get "https://aur.archlinux.org/rpc?v=5&type=info&arg[]python-terminaltextffects": dial tcp 95.216.194.15:443: i/o timeout ''' Context & Analysis: My local internet connection was confirmed to be stable and working (e.g., ping google.com was successful with 0% packet loss). The issue appears to be an i/o timeout and unexpected eof when the script attempts a TLS handshake with aur.archlinux.org. This suggests a potential issue with the AUR server itself or a network problem on their end, rather than a problem with the user's connection. 
- IMG_20250813_113520_hdr.jpg
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.