Proof Portal

Sign in
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-647GitHub issuePublicDecided· Out of scope

Limine autoboot is cancelled by mouse movement

Reported by rva79 · filed Sep 12, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 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

Limine autoboot is cancelled by mouse movementrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

AMD Ryzen 7 9800X3D, NVIDIA GeForce RTX 5090, Omarchy 4.0.0.r2100.gb5589fa-1, Limine 12.9.0, kernel 7.2.4-arch1-2. Desktop with a USB optical mouse left plugged in.

What's wrong?

On every power-on the Omarchy Bootloader menu appears, a mouse cursor moves across the entries, the autoboot countdown stops, and the machine sits there until I arrow to linux and press Enter.

Expected: the default linux entry boots after the timeout, with the keyboard still available for snapshots.

Actual: any pointer motion is treated as input. Optical mice often twitch at POST; that is enough to abort the countdown. After that the selection follows the pointer, so the highlighted entry is often not linux.

This is Limine's documented behaviour, not a firmware glitch. From Limine CONFIG.md:

mouse — If set to no, disable mouse support in the boot menu. Defaults to yes […]. Using the mouse stops the timeout countdown, as pressing a key does.

Mouse support landed in Limine 12.5.0. Omarchy's packaged default never opts out:

https://github.com/omacom/omarchy/blob/master/default/limine/limine.conf

#timeout: 3 is commented, so Limine's 5s default applies, and there is no mouse: line. omarchy-refresh-limine copies that file onto /boot/limine.conf.

omarchy debug is not useful here: the hang is in Limine, before the kernel.

Workaround

Add this to /boot/limine.conf (global options, before the first / entry):

mouse: no

Keyboard still selects snapshots. Set mouse: yes if you want the pointer.

Suggested fix

  1. Add mouse: no to default/limine/limine.conf (new installs and omarchy-refresh-limine).
  2. A migration that inserts mouse: no into existing /boot/limine.conf if the option is missing (current installs on the next omarchy update).

I searched omacom/omarchy issues, PRs, and discussions for this and did not find an existing report. Closest Limine ticket is #618 (mouse blocks the keyboard on Snapdragon firmware), which is a different symptom.

View raw text
### System details

AMD Ryzen 7 9800X3D, NVIDIA GeForce RTX 5090, Omarchy 4.0.0.r2100.gb5589fa-1, Limine 12.9.0, kernel 7.2.4-arch1-2. Desktop with a USB optical mouse left plugged in.

### What's wrong?

On every power-on the **Omarchy Bootloader** menu appears, a mouse cursor moves across the entries, the autoboot countdown stops, and the machine sits there until I arrow to `linux` and press Enter.

**Expected:** the default `linux` entry boots after the timeout, with the keyboard still available for snapshots.

**Actual:** any pointer motion is treated as input. Optical mice often twitch at POST; that is enough to abort the countdown. After that the selection follows the pointer, so the highlighted entry is often not `linux`.

This is Limine's documented behaviour, not a firmware glitch. From [Limine CONFIG.md](https://github.com/Limine-Bootloader/Limine/blob/trunk/CONFIG.md):

> `mouse` — If set to `no`, disable mouse support in the boot menu. Defaults to `yes` […]. Using the mouse stops the `timeout` countdown, as pressing a key does.

Mouse support landed in Limine 12.5.0. Omarchy's packaged default never opts out:

https://github.com/omacom/omarchy/blob/master/default/limine/limine.conf

`#timeout: 3` is commented, so Limine's 5s default applies, and there is no `mouse:` line. `omarchy-refresh-limine` copies that file onto `/boot/limine.conf`.

`omarchy debug` is not useful here: the hang is in Limine, before the kernel.

#### Workaround

Add this to `/boot/limine.conf` (global options, before the first `/` entry):

```
mouse: no
```

Keyboard still selects snapshots. Set `mouse: yes` if you want the pointer.

#### Suggested fix

1. Add `mouse: no` to `default/limine/limine.conf` (new installs and `omarchy-refresh-limine`).
2. A migration that inserts `mouse: no` into existing `/boot/limine.conf` if the option is missing (current installs on the next `omarchy update`).

I searched omacom/omarchy issues, PRs, and discussions for this and did not find an existing report. Closest Limine ticket is [#618](https://github.com/Limine-Bootloader/Limine/issues/618) (mouse blocks the keyboard on Snapdragon firmware), which is a different symptom.

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 12:10 UTC