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

`omarchy update` will always prompt for reboot if more than one kernel installed

Reported by wrnlb666 · filed May 4, 2026Closed upstream on 2026-05-04 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

`omarchy update` will always prompt for reboot if more than one kernel installedrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Any System

What's wrong?

The current implementation of bin/omarchy-update-restart have these lines

running_kernel=$(uname -r)
kernel_updated=false

for kernel in /usr/lib/modules/*/vmlinuz; do
  if [[ -f $kernel ]] && pacman -Qo "$kernel" &>/dev/null; then
    installed_kernel=$(basename "$(dirname "$kernel")")

    if [[ $installed_kernel != $running_kernel ]]; then
      kernel_updated=true
      break
    fi
  fi
done

which that if there's only one kernel installed, everything is fine. But if more than one kernels are installed, kernel_updated will always be set to true, shoudn't it be changed to this? 

running_kernel=$(uname -r)
kernel_updated=true

for kernel in /usr/lib/modules/*/vmlinuz; do
  if [[ -f $kernel ]] && pacman -Qo "$kernel" &>/dev/null; then
    installed_kernel=$(basename "$(dirname "$kernel")")

    if [[ $installed_kernel == $running_kernel ]]; then
      kernel_updated=false
      break
    fi
  fi
done
View raw text
### System details

Any System

### What's wrong?

The current implementation of `bin/omarchy-update-restart` have these lines
```bash
running_kernel=$(uname -r)
kernel_updated=false

for kernel in /usr/lib/modules/*/vmlinuz; do
  if [[ -f $kernel ]] && pacman -Qo "$kernel" &>/dev/null; then
    installed_kernel=$(basename "$(dirname "$kernel")")

    if [[ $installed_kernel != $running_kernel ]]; then
      kernel_updated=true
      break
    fi
  fi
done
```
which that if there's only one kernel installed, everything is fine. But if more than one kernels are installed, `kernel_updated` will always be set to `true`, shoudn't it be changed to this? 
```bash
running_kernel=$(uname -r)
kernel_updated=true

for kernel in /usr/lib/modules/*/vmlinuz; do
  if [[ -f $kernel ]] && pacman -Qo "$kernel" &>/dev/null; then
    installed_kernel=$(basename "$(dirname "$kernel")")

    if [[ $installed_kernel == $running_kernel ]]; then
      kernel_updated=false
      break
    fi
  fi
done
```

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.