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

False low battery notification on boot

Reported by data-davey · filed Oct 26, 2025Closed upstream on 2025-10-29 by its own reporter data-davey. GitHub close reason: completed. Closed by its own reporter — not by itself 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

False low battery notification on bootrevision 1 · captured 2026-10-04 11:42 UTC via poll

System details

Framework laptop 13, AMD Ryzen AI 7 350, Omarchy 3.1.3, linux 6.17.5-arch1-1

What's wrong?

Bug Report: False low battery notification on boot

Description:
When booting on battery power with >90% charge, I receive a false notification that the battery is at 0% and needs recharging.

Root Cause:
During early boot, omarchy-battery-remaining may return an empty value before the battery subsystem is fully initialised. When BATTERY_LEVEL is empty, bash's numeric comparison -le treats it as 0, triggering the false notification.

Reproduction:
1. Ensure battery is >90% charged
2. Boot laptop on battery power
3. Observe false "Battery is down to 0%" notification

Proposed Fix:
Add validation to check if BATTERY_LEVEL is empty or non-numeric before performing comparisons:

# Exit early if battery level is empty or not a valid number
if [[ -z "$BATTERY_LEVEL" ]] || ! [[ "$BATTERY_LEVEL" =~ ^[0-9]+$ ]]; then
  exit 0
fi

This prevents false notifications during boot while maintaining correct behavior when battery is genuinely low.

Testing:
- Verified script works correctly when run manually
- Added validation prevents false positives during boot
- Confirmed real low-battery notifications still work by temporarily raising threshold

View raw text
### System details

Framework laptop 13, AMD Ryzen AI 7 350, Omarchy 3.1.3, linux 6.17.5-arch1-1

### What's wrong?

### Bug Report: False low battery notification on boot

**Description:**
When booting on battery power with >90% charge, I receive a false notification that the battery is at 0% and needs recharging.

**Root Cause:**
During early boot, `omarchy-battery-remaining` may return an empty value before the battery subsystem is fully initialised. When `BATTERY_LEVEL` is empty, bash's numeric comparison `-le` treats it as 0, triggering the false notification.

**Reproduction:**
1. Ensure battery is >90% charged
2. Boot laptop on battery power
3. Observe false "Battery is down to 0%" notification

**Proposed Fix:**
Add validation to check if `BATTERY_LEVEL` is empty or non-numeric before performing comparisons:
```bash
# Exit early if battery level is empty or not a valid number
if [[ -z "$BATTERY_LEVEL" ]] || ! [[ "$BATTERY_LEVEL" =~ ^[0-9]+$ ]]; then
  exit 0
fi
```

This prevents false notifications during boot while maintaining correct behavior when battery is genuinely low.

**Testing:**
- Verified script works correctly when run manually
- Added validation prevents false positives during boot
- Confirmed real low-battery notifications still work by temporarily raising threshold

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.