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-1297GitHub issuePublicDecided· Out of scope

Low-battery notification remains after charger is connected

Reported by pixelpush-io · filed Aug 28, 2026 · open at source

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

Low-battery notification remains after charger is connectedrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

  • Lenovo ThinkPad L13 Gen 2 (20VH004EUK)
  • Intel Core i5-1135G7 / Intel Iris Xe Graphics
  • Omarchy 4.0.0-1
  • Hyprland 0.56.2
  • quickshell-git 0.3.0.r20.g28771c7-1
  • UPower 1.91.3-1

What is wrong?

The persistent critical Time to recharge! notification does not automatically disappear after connecting the charger. It remains on screen until it is manually dismissed, even though UPower has transitioned from discharging to charging.

This is the normal same-session transition after a genuine low-battery warning, not the startup race described in #7679.

Steps to reproduce

  1. Run on battery until the level reaches 10%.
  2. Observe the Time to recharge! notification.
  3. Connect the charger and confirm that the battery state changes to charging.
  4. Observe that the notification remains until manually dismissed.

Expected

The low-battery warning should be dismissed automatically once AC power is connected and UPower.onBattery becomes false.

Actual

The warning remains visible indefinitely until manually dismissed.

Verification and likely cause

The notification history confirms that the warning was emitted at 10%. After connecting AC, UPower reports state: charging; the warning still required manual dismissal.

bin/omarchy-battery-low sends the warning with critical urgency. The notification service treats critical notifications as persistent. In shell/plugins/services/battery/Service.qml, onOnBatteryChanged() calls checkBattery() and applyPowerProfile(), but it does not dismiss the existing warning when switching to AC.

Omarchy already exposes omarchy notification dismiss <summary>, so the AC transition could dismiss the Time to recharge! warning explicitly.

Related but distinct: #7679.

View raw text
## System details

- Lenovo ThinkPad L13 Gen 2 (20VH004EUK)
- Intel Core i5-1135G7 / Intel Iris Xe Graphics
- Omarchy 4.0.0-1
- Hyprland 0.56.2
- quickshell-git 0.3.0.r20.g28771c7-1
- UPower 1.91.3-1

## What is wrong?

The persistent critical `Time to recharge!` notification does not automatically disappear after connecting the charger. It remains on screen until it is manually dismissed, even though UPower has transitioned from discharging to charging.

This is the normal same-session transition after a genuine low-battery warning, not the startup race described in #7679.

### Steps to reproduce

1. Run on battery until the level reaches 10%.
2. Observe the `Time to recharge!` notification.
3. Connect the charger and confirm that the battery state changes to charging.
4. Observe that the notification remains until manually dismissed.

### Expected

The low-battery warning should be dismissed automatically once AC power is connected and `UPower.onBattery` becomes false.

### Actual

The warning remains visible indefinitely until manually dismissed.

## Verification and likely cause

The notification history confirms that the warning was emitted at 10%. After connecting AC, UPower reports `state: charging`; the warning still required manual dismissal.

`bin/omarchy-battery-low` sends the warning with critical urgency. The notification service treats critical notifications as persistent. In `shell/plugins/services/battery/Service.qml`, `onOnBatteryChanged()` calls `checkBattery()` and `applyPowerProfile()`, but it does not dismiss the existing warning when switching to AC.

Omarchy already exposes `omarchy notification dismiss <summary>`, so the AC transition could dismiss the `Time to recharge!` warning explicitly.

Related but distinct: #7679.

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 09:47 UTC