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-414GitHub issuePublicDecided· Out of scope

sudo password prompt in foot intermittently rejects the correct password — PAM logs "conversation failed", typed input never reaches sudo

Reported by artinlenz · filed Sep 17, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

sudo password prompt in foot intermittently rejects the correct password — PAM logs "conversation failed", typed input never reaches sudorevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Apple MacBook Pro 14" M2 Max (2023, aarch64/Asahi), Omarchy 4.0.3-mac.1 (omarchy-dev 4.0.3.r6962, Apple Silicon build), Hyprland 0.56.2, foot 1.28.0, sudo 1.9.17p2, fcitx5 5.1.22

What's wrong?

What happened

Typing the correct password at a sudo prompt in foot was rejected repeatedly over a ~30 minute window. On screen sudo showed Sorry, try again., but the journal does not show wrong-password rejections — it shows PAM conversation failed / auth could not identify password, i.e. sudo's password read on the tty ended without a usable response. In one case the same sudo process logged a genuine authentication failure and then, exactly 5 minutes later (sudo's default passwd_timeout), a conversation failed — so the password/Enter typed at the second prompt never reached sudo at all. A few minutes later the identical password was accepted and every subsequent prompt worked on the first try.

Journal (journalctl -o short-precise | grep 'sudo\[', hostname redacted):

13:02:27.877 sudo[82291]: pam_unix(sudo:auth): authentication failure; logname=artin uid=1000 euid=0 tty=/dev/pts/1 ruser=artin rhost=  user=artin
13:07:29.901 sudo[82291]: pam_unix(sudo:auth): conversation failed
13:07:29.901 sudo[82291]: pam_unix(sudo:auth): auth could not identify password for [artin]
13:07:31.927 sudo[82291]:    artin : 4 incorrect password attempts ; TTY=pts/1 ; PWD=... ; USER=root ; COMMAND=/usr/bin/pacman -S ...

13:15:52.161 sudo[105969]: pam_unix(sudo:auth): conversation failed
13:15:52.161 sudo[105969]: pam_unix(sudo:auth): auth could not identify password for [artin]
13:15:54.195 sudo[105969]:    artin : 1 incorrect password attempt ; TTY=pts/1 ; ...

13:20:02.729 sudo[112447]: pam_unix(sudo:auth): conversation failed
13:20:02.729 sudo[112447]: pam_unix(sudo:auth): auth could not identify password for [artin]
13:20:04.832 sudo[112447]:    artin : 1 incorrect password attempt ; TTY=pts/1 ; ...

13:32:00.351 sudo[130829]:    artin : TTY=pts/1 ; PWD=... ; USER=root ; COMMAND=/usr/bin/pacman -S ...   <- same password, accepted
13:32:00.353 sudo[130829]: pam_unix(sudo:session): session opened for user root(uid=0) by artin(uid=1000)

Terminal at the time (sudo pid 130829, before it finally accepted the password):

[artin@artin pkg]$ sudo pacman -S --needed --noconfirm patchelf ayatana-ido libayatana-indicator && makepkg -si --noconfirm
[sudo] password for artin:
Sorry, try again.
[sudo] password for artin:
Sorry, try again.
[sudo] password for artin: _

Nothing else typed into the same foot window was lost — the command lines themselves arrived fine; only input while the tty was in no-echo password mode went missing. Side effect: every aborted prompt is counted by pam_faillock as a failed login.

Expected

The correct password + Enter at a sudo prompt in foot authenticates on the first try, every time.

Steps to reproduce

Not reliably reproducible, unfortunately. What I have:

  1. Omarchy default config, fcitx5 running (omarchy-fcitx5.service), foot opened with Super+Return.
  2. sudo <anything> → type password → Enter.
  3. During the affected window (~13:00–13:32) 5 of 6 prompts failed as above; from 13:32 on, all prompts (incl. two makepkg sudo prompts seconds later) succeeded.
  4. A later controlled test (sudo -k; sudo true, password typed once) succeeded both with fcitx5 running and with omarchy-fcitx5.service stopped — so I could not pin it on fcitx5, although it is notable that with fcitx5 running Hyprland reports hl-virtual-keyboard-fcitx5 as the main keyboard (all key input reaches the terminal via the IM's virtual keyboard); with it stopped the physical apple-mtp-keyboard becomes main.

Possibly related (same PAM signature, but via the Quickshell polkit dialog rather than a tty): #8924.

System details

  • Omarchy 4.0.3-mac.1 — package omarchy-dev 4.0.3.r6962.ga67d7f7-1 (Apple Silicon build, https://github.com/maralcbr/omarchy-mx-mac); config is stock Omarchy, ~/.config/hypr/input.lua untouched
  • Apple MacBook Pro 14" M2 Max (2023, Mac14,5), aarch64, Arch Linux ARM / Asahi kernel 7.1.13-3-1-ARCH
  • Hyprland 0.56.2-3, foot 1.28.0-2, bash, SDDM
  • sudo 1.9.17.p2-6, pam 1.7.2-2 — /etc/pam.d/sudo and system-auth stock (pam_faillock deny=10 unlock_time=120, pam_unix try_first_pass nullok); no /etc/sudoers.d overrides, no passwd_timeout/pwfeedback/use_pty
  • fcitx5 5.1.22-1 (INPUT_METHOD=fcitx, XMODIFIERS=@im=fcitx, QT_IM_MODULE=fcitx, SDL_IM_MODULE=fcitx), profile: single group, keyboard-us
  • Layout: us / English (US); locale en_US.UTF-8
  • hyprctl devices keyboards: apple-mtp-keyboard (main: false), hl-virtual-keyboard-fcitx5 (main: true)

omarchy-debug --no-sudo --print output available on request (it contains MAC addresses / firewall lines I'd rather not paste publicly). Happy to run any further diagnostics.

View raw text
### System details

Apple MacBook Pro 14" M2 Max (2023, aarch64/Asahi), Omarchy 4.0.3-mac.1 (omarchy-dev 4.0.3.r6962, Apple Silicon build), Hyprland 0.56.2, foot 1.28.0, sudo 1.9.17p2, fcitx5 5.1.22

### What's wrong?

## What happened

Typing the correct password at a `sudo` prompt in foot was rejected repeatedly over a ~30 minute window. On screen sudo showed `Sorry, try again.`, but the journal does **not** show wrong-password rejections — it shows PAM `conversation failed` / `auth could not identify password`, i.e. sudo's password read on the tty ended without a usable response. In one case the same sudo process logged a genuine `authentication failure` and then, exactly 5 minutes later (sudo's default `passwd_timeout`), a `conversation failed` — so the password/Enter typed at the second prompt never reached sudo at all. A few minutes later the identical password was accepted and every subsequent prompt worked on the first try.

Journal (`journalctl -o short-precise | grep 'sudo\['`, hostname redacted):

```
13:02:27.877 sudo[82291]: pam_unix(sudo:auth): authentication failure; logname=artin uid=1000 euid=0 tty=/dev/pts/1 ruser=artin rhost=  user=artin
13:07:29.901 sudo[82291]: pam_unix(sudo:auth): conversation failed
13:07:29.901 sudo[82291]: pam_unix(sudo:auth): auth could not identify password for [artin]
13:07:31.927 sudo[82291]:    artin : 4 incorrect password attempts ; TTY=pts/1 ; PWD=... ; USER=root ; COMMAND=/usr/bin/pacman -S ...

13:15:52.161 sudo[105969]: pam_unix(sudo:auth): conversation failed
13:15:52.161 sudo[105969]: pam_unix(sudo:auth): auth could not identify password for [artin]
13:15:54.195 sudo[105969]:    artin : 1 incorrect password attempt ; TTY=pts/1 ; ...

13:20:02.729 sudo[112447]: pam_unix(sudo:auth): conversation failed
13:20:02.729 sudo[112447]: pam_unix(sudo:auth): auth could not identify password for [artin]
13:20:04.832 sudo[112447]:    artin : 1 incorrect password attempt ; TTY=pts/1 ; ...

13:32:00.351 sudo[130829]:    artin : TTY=pts/1 ; PWD=... ; USER=root ; COMMAND=/usr/bin/pacman -S ...   <- same password, accepted
13:32:00.353 sudo[130829]: pam_unix(sudo:session): session opened for user root(uid=0) by artin(uid=1000)
```

Terminal at the time (sudo pid 130829, before it finally accepted the password):

```
[artin@artin pkg]$ sudo pacman -S --needed --noconfirm patchelf ayatana-ido libayatana-indicator && makepkg -si --noconfirm
[sudo] password for artin:
Sorry, try again.
[sudo] password for artin:
Sorry, try again.
[sudo] password for artin: _
```

Nothing else typed into the same foot window was lost — the command lines themselves arrived fine; only input while the tty was in no-echo password mode went missing. Side effect: every aborted prompt is counted by `pam_faillock` as a failed login.

## Expected

The correct password + Enter at a sudo prompt in foot authenticates on the first try, every time.

## Steps to reproduce

Not reliably reproducible, unfortunately. What I have:

1. Omarchy default config, fcitx5 running (`omarchy-fcitx5.service`), foot opened with Super+Return.
2. `sudo <anything>` → type password → Enter.
3. During the affected window (~13:00–13:32) 5 of 6 prompts failed as above; from 13:32 on, all prompts (incl. two `makepkg` sudo prompts seconds later) succeeded.
4. A later controlled test (`sudo -k; sudo true`, password typed once) succeeded both with fcitx5 running and with `omarchy-fcitx5.service` stopped — so I could not pin it on fcitx5, although it is notable that with fcitx5 running Hyprland reports `hl-virtual-keyboard-fcitx5` as the **main** keyboard (all key input reaches the terminal via the IM's virtual keyboard); with it stopped the physical `apple-mtp-keyboard` becomes main.

Possibly related (same PAM signature, but via the Quickshell polkit dialog rather than a tty): #8924.

## System details

- Omarchy `4.0.3-mac.1` — package `omarchy-dev 4.0.3.r6962.ga67d7f7-1` (Apple Silicon build, https://github.com/maralcbr/omarchy-mx-mac); config is stock Omarchy, `~/.config/hypr/input.lua` untouched
- Apple MacBook Pro 14" M2 Max (2023, Mac14,5), aarch64, Arch Linux ARM / Asahi kernel `7.1.13-3-1-ARCH`
- Hyprland 0.56.2-3, foot 1.28.0-2, bash, SDDM
- sudo 1.9.17.p2-6, pam 1.7.2-2 — `/etc/pam.d/sudo` and `system-auth` stock (`pam_faillock deny=10 unlock_time=120`, `pam_unix try_first_pass nullok`); no `/etc/sudoers.d` overrides, no `passwd_timeout`/`pwfeedback`/`use_pty`
- fcitx5 5.1.22-1 (`INPUT_METHOD=fcitx`, `XMODIFIERS=@im=fcitx`, `QT_IM_MODULE=fcitx`, `SDL_IM_MODULE=fcitx`), profile: single group, `keyboard-us`
- Layout: us / English (US); locale en_US.UTF-8
- `hyprctl devices` keyboards: `apple-mtp-keyboard` (main: false), `hl-virtual-keyboard-fcitx5` (main: **true**)

`omarchy-debug --no-sudo --print` output available on request (it contains MAC addresses / firewall lines I'd rather not paste publicly). Happy to run any further diagnostics.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 14:51 UTC