Proof Portal

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

install fails on omarchy 3.2 with limine-snapper script expecting /boot/limine/limine.conf

Reported by ZarK · filed Nov 22, 2025Closed upstream on 2026-10-08 by the bot omarchybot, as not planned.

Open at source

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

install fails on omarchy 3.2 with limine-snapper script expecting /boot/limine/limine.confrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Surface Book 2

What's wrong?

Surface Book 2, so after archinstall using the setup from https://learn.omacom.io/2/the-omarchy-manual/96/manual-installation, I follow the guide from surface-linux here https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup.

Since I was hit by #3335 during my last install attempt some weeks ago I moved /boot/EFI/limine/limine.conf to /boot/limine.conf this time, even though the issue was closed. Update limine.conf to add entry with surface-linux and reboot with secure boot works fine.

During omarchy 3.2 install, I see

Updated: /boot/limine.conf

which makes me happy. However, it is followed by:

v Signed /boot/EFI/limine/limine_x64.efi
(5/7) Reloading system bus configuration
(6/7) Updating icon theme caches...
(7/7) Updating the desktop file MIME type cache...
Error: Limine config not found at /boot/limine/limine.conf

This command halted with exit code 0:
Failed script: /home/zark/.local/share/omarchy/install/login/limine-snapper.sh

There was no /boot/limine/limine.conf after archinstall and I did not move it there, so I guess that is correct - but then why does it fail on this path?

I have no folder /boot/limine/

The install seems to have updated /boot/limine.conf properly and there is the expected /boot/limine.conf.old as well.

I see in limine-snapper.sh that it really does fall back to that path:
https://github.com/basecamp/omarchy/blob/master/install/login/limine-snapper.sh#L10-L20

  # Conf location is different between EFI and BIOS
  if [[ -n "$EFI" ]]; then
    # Check USB location first, then regular EFI location
    if [[ -f /boot/EFI/BOOT/limine.conf ]]; then
      limine_config="/boot/EFI/BOOT/limine.conf"
    else
      limine_config="/boot/EFI/limine/limine.conf"
    fi
  else
    limine_config="/boot/limine/limine.conf"
  fi

But why?

Changing the fallback to

  else
    limine_config="/boot/limine.conf"
  fi

fixed the issue for me and the install script successfully ran afterwards.

View raw text

### System details

Surface Book 2

### What's wrong?

Surface Book 2, so after archinstall using the setup from https://learn.omacom.io/2/the-omarchy-manual/96/manual-installation, I follow the guide from surface-linux here https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup.

Since I was hit by #3335 during my last install attempt some weeks ago I moved /boot/EFI/limine/limine.conf to /boot/limine.conf this time, even though the issue was closed. Update limine.conf to add entry with surface-linux and reboot with secure boot works fine.

During omarchy 3.2 install, I see

`Updated: /boot/limine.conf`

which makes me happy. However, it is followed by:

```
v Signed /boot/EFI/limine/limine_x64.efi
(5/7) Reloading system bus configuration
(6/7) Updating icon theme caches...
(7/7) Updating the desktop file MIME type cache...
Error: Limine config not found at /boot/limine/limine.conf

This command halted with exit code 0:
Failed script: /home/zark/.local/share/omarchy/install/login/limine-snapper.sh
```

There was no /boot/limine/limine.conf after archinstall and I did not move it there, so I guess that is correct - but then why does it fail on this path? 

I have no folder `/boot/limine/`

The install seems to have updated `/boot/limine.conf `properly and there is the expected `/boot/limine.conf.old `as well.

I see in limine-snapper.sh that it really does fall back to that path:
https://github.com/basecamp/omarchy/blob/master/install/login/limine-snapper.sh#L10-L20

```
  # Conf location is different between EFI and BIOS
  if [[ -n "$EFI" ]]; then
    # Check USB location first, then regular EFI location
    if [[ -f /boot/EFI/BOOT/limine.conf ]]; then
      limine_config="/boot/EFI/BOOT/limine.conf"
    else
      limine_config="/boot/EFI/limine/limine.conf"
    fi
  else
    limine_config="/boot/limine/limine.conf"
  fi
```

But why?

Changing the fallback to 
```
  else
    limine_config="/boot/limine.conf"
  fi
```

fixed the issue for me and the install script successfully ran afterwards.

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.

Proof

History & reports

Reference