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

Drive decryption password is not being accepted

Reported by Dimonoy · filed Jan 23, 2026Closed upstream on 2026-01-25 by its own reporter Dimonoy. GitHub close reason: completed. Closed by its own reporter — not by itself 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

Drive decryption password is not being acceptedrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

Lenovo Inspiron 15, Kernel 6.17.8-arch1-1, Omarcy Image Version 2025.11.26

What's wrong?

I have encountered a similar issue to the https://github.com/basecamp/omarchy/issues/651.

Problem: Today I booted my system and after confirming in Limine the default Linux EFI boot option the password menu prompted, as usual. I entered my correct ASCII-friendly password, as usual, and ... the loading bar got interrupted prompting me to input password again. I click ctrl+alt+f8 to see the output:

No key available with this passphrase
A password is required to access the root volume:

After several attempts and making sure the password I entered is correct I clicked ctrl+C just for fun:

ERROR: Password succeeded, but root creation failed, aborting...

After a while I got into the emergency shell with the following message:

ERROR: Failed to mount '/dev/mapper/root' on real root.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off

Attempts: There were no necessary files or tools that could allow proper diagnosis, so I booted from USB Live and successfully opened the LUKS crypted partition that prompts password with cryptsetup tool entering the same passphrase. I mounted the boot partition and the encrypted partition, arch-chrooted into it. All the tools and files were there, I confirmed there is no data corruption and nothing is broken. The PARTUUID signifying the encrypted disk is consistent with what blkid and cat /boot/limine.conf showed.

Adding new passphrase with cryptsetup luksAddKey didn't yield any improvements.

I also attempted to create a keyfile and specified it in /etc/mkinitcpio.conf:FILES, but I am not sure where and how to configure anything to use that file on boot. It doesn't seem as a long-term solution as well.

Shortly the issue is: password prompt after limine boot menu doesn't accept my correct password anymore.

I will provide an additional information if necessary.

View raw text
### System details

Lenovo Inspiron 15, Kernel 6.17.8-arch1-1, Omarcy Image Version 2025.11.26

### What's wrong?

I have encountered a similar issue to the https://github.com/basecamp/omarchy/issues/651.

**Problem**: Today I booted my system and after confirming in Limine the default Linux EFI boot option the password menu prompted, as usual. I entered my correct ASCII-friendly password, as usual, and ... the loading bar got interrupted prompting me to input password again. I click `ctrl+alt+f8` to see the output:

```
No key available with this passphrase
A password is required to access the root volume:
```

After several attempts and making sure the password I entered is correct I clicked `ctrl+C` just for fun:

```
ERROR: Password succeeded, but root creation failed, aborting...
```

After a while I got into the emergency shell with the following message:

```
ERROR: Failed to mount '/dev/mapper/root' on real root.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
```

**Attempts**: There were no necessary files or tools that could allow proper diagnosis, so I booted from USB Live and successfully opened the LUKS crypted partition that prompts password with `cryptsetup` tool entering the same passphrase. I mounted the boot partition and the encrypted partition, `arch-chroot`ed into it. All the tools and files were there, I confirmed there is no data corruption and nothing is broken. The PARTUUID signifying the encrypted disk is consistent with what `blkid` and `cat /boot/limine.conf` showed.

Adding new passphrase with `cryptsetup luksAddKey` didn't yield any improvements.

I also attempted to create a keyfile and specified it in `/etc/mkinitcpio.conf:FILES`, but I am not sure where and how to configure anything to use that file on boot. It doesn't seem as a long-term solution as well.

**Shortly the issue is**: password prompt after limine boot menu doesn't accept my correct password anymore.

I will provide an additional information if necessary.

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.