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

Omarchy 3.2.3: migration fails with "limine-update: command not found"

Reported by marcinczenko · filed Dec 16, 2025Closed upstream on 2025-12-16 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not 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

Omarchy 3.2.3: migration fails with "limine-update: command not found"revision 1 · captured 2026-10-04 11:49 UTC via poll

System details

FW Laptop 13 (AMD Ryzen AI 300 Series) (A9)

What's wrong?

when updating omarchy to version 3.2.3, one of the migration failed with error limine-update: command not found. Looking at the code, it might be 1758455816.sh:

echo "Add thunderbolt support to boot image"

omarchy-pkg-add bolt

if [[ ! -f /etc/mkinitcpio.conf.d/thunderbolt_module.conf ]]; then
  sudo tee /etc/mkinitcpio.conf.d/thunderbolt_module.conf <<EOF >/dev/null
MODULES+=(thunderbolt)
EOF
fi

sudo limine-update

This command missing may be a normal thing in my installation as my Omarchy does not use limine... (it was installed when limine was not yet used by Omarchy).

I can get limine-update command installed with omarchy-pkg-add limine-entry-tool but it will not be used anyway, as I am not using limine.

I am worried about other thing: I am using systemd-boot. Does it mean that I am not getting any relevant updates anymore? What is recommendation? Move to limine (as far as I know this have to be done manually - there is no support script to help with the trasisiton...).

View raw text
### System details

FW Laptop 13 (AMD Ryzen AI 300 Series) (A9)

### What's wrong?

when updating omarchy to version `3.2.3`, one of the migration failed with error `limine-update: command not found`. Looking at the code, it might be `1758455816.sh`:

```bash
echo "Add thunderbolt support to boot image"

omarchy-pkg-add bolt

if [[ ! -f /etc/mkinitcpio.conf.d/thunderbolt_module.conf ]]; then
  sudo tee /etc/mkinitcpio.conf.d/thunderbolt_module.conf <<EOF >/dev/null
MODULES+=(thunderbolt)
EOF
fi

sudo limine-update
```

This command missing may be a normal thing in my installation as my Omarchy does not use limine... (it was installed when limine was not yet used by Omarchy).

I can get limine-update command installed with `omarchy-pkg-add limine-entry-tool` but it will not be used anyway, as I am not using limine.

I am worried about other thing: I am using `systemd-boot`. Does it mean that I am not getting any relevant updates anymore? What is recommendation? Move to limine (as far as I know this have to be done manually - there is no support script to help with the trasisiton...).

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.