Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Desktop notification showing incorrect battery percentage on dual battery systems
Reported by Michael-Steshenko · filed May 12, 2026Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
System details
ThinkPad T480
What's wrong?
The battery percentage showed in the waybar correctly shows the unified battery level from both batteries.
When you right click the battery icon in the waybar, it runs the omarchy-battery-status script, which gets the battery information only for BAT0:
battery_info=$(upower -i $(upower -e | grep BAT))This results in inconsistent battery reading between what is shown in the waybar and the notification when you right click it.
Video showing the issue:
https://github.com/user-attachments/assets/d12dc8c7-rbf0a-496d-a84e-b558cefae0fe
Ignore the rounding error between 82% and 81% that is a separate, pre-existing issue.
Suggested fix
There are 2 ways of fixing this I think could work here, happy to hear opinions.
1. just show the unified reading in the desktop notification by changing
battery_info=$(upower -i $(upower -e | grep BAT))to
battery_info=$(upower -i /org/freedesktop/UPower/devices/DisplayDevice)see info about /org/freedesktop/UPower/devices/DisplayDevice
- Alternatively we could display the information for each battery in a separate row in the desktop notification.
I am happy to create a PR for either solution.
View raw text
### System details ThinkPad T480 ### What's wrong? The battery percentage showed in the waybar correctly shows the unified battery level from both batteries. When you right click the battery icon in the waybar, it runs the [omarchy-battery-status script](https://github.com/basecamp/omarchy/blob/dev/bin/omarchy-battery-status), which gets the battery information only for BAT0: ``` battery_info=$(upower -i $(upower -e | grep BAT)) ``` This results in inconsistent battery reading between what is shown in the waybar and the notification when you right click it. Video showing the issue: https://github.com/user-attachments/assets/d12dc8c7-rbf0a-496d-a84e-b558cefae0fe Ignore the rounding error between 82% and 81% that is a separate, pre-existing issue. ### Suggested fix There are 2 ways of fixing this I think could work here, happy to hear opinions. 1. just show the unified reading in the desktop notification by changing ``` battery_info=$(upower -i $(upower -e | grep BAT)) ``` to ``` battery_info=$(upower -i /org/freedesktop/UPower/devices/DisplayDevice) ``` see info about [/org/freedesktop/UPower/devices/DisplayDevice](https://upower.freedesktop.org/docs/UPower.html) 2. Alternatively we could display the information for each battery in a separate row in the desktop notification. I am happy to create a PR for either solution.
- d12dc8c7-rbf0a-496d-a84e-b558cefae0fe
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.