OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
power-suspend medium occasional DISPUTE

Clear a 'Time to recharge!' notification that repeats every few seconds or stays after plugging in

omarchylaptopusb-cupower
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Read #9670 (open), #8813 (open, with the maintainer bot's confirmation) and PR #9883 (open, unmerged, labelled ready). The issue supports the 3 to 4 second cadence, the ucsi_acpi USBC000:00: unknown error 256 line, the alternating ACAD udev events and the latch mechanism. Confirmed on this workstation that BatteryModel.js recomputes notifiedLowBattery: low and is byte-identical to quattro, that Service.qml calls checkBattery() from onOnBatteryChanged, and that shell/plugins/notifications/Service.qml durationFor() returns 0 (never expires) for critical urgency, so the -t 30000 that /usr/bin/omarchy-battery-low passes is discarded. Nothing dismisses the toast on AC connect. Super+Shift+Comma is bound to dismissAll in both the installed and quattro utilities.lua (the binding syntax differs between them, the key does not). omarchy-notification-dismiss exists in /usr/bin and dismisses by summary substring through omarchy-shell. One related path the record does not mention, from #8813's comments: a critical toast persisted under ~/.local/state/omarchy/notifications/ is restored after a shell restart or reboot even on AC. The same dismiss command clears it, so the fix still covers it. The flap diagnosis commands are read-only. Nothing was exercised on hardware.

Symptom

Near empty, Omarchy shows "Time to recharge! Battery is down to N%" every 3 to 4 seconds, and hundreds of them pile up on screen. Or a single warning stays on screen after the charger is connected and the battery shows charging, until it is dismissed by hand. The kernel log during the storm shows ucsi_acpi USBC000:00: unknown error 256, and the AC adapter's udev events alternate between plugged and unplugged.

Cause

In BatteryModel.js, the notified latch is recomputed as notifiedLowBattery: low on every check, and Service.qml runs checkBattery() from onOnBatteryChanged. When the AC online status flaps, which is a USB-C power-delivery or UCSI fault, each flap runs one check that sees AC and clears the latch and one that sees battery and notifies again. The warning is sent with critical urgency, and Omarchy's notification service keeps critical notifications until they are dismissed. Nothing dismisses the warning when the charger connects either. BatteryModel.js is unchanged on 4.0.4-1 and quattro. The latch fix, PR #9883, is open and unmerged.

Fix

**Dismiss them.** Super+Shift+Comma dismisses all notifications. From a terminal, by summary substring:


omarchy-notification-dismiss "Time to recharge"

**Find the flapping supply.** The storm is caused by the power supply bouncing, so watch it directly:


journalctl -k -b | grep -i ucsi
udevadm monitor --subsystem-match=power_supply

If the AC device toggles every few seconds, reseat the USB-C cable, try another port or another charger, and check the laptop vendor's firmware updates for USB-C power-delivery fixes. Once the supply stops flapping, the latch holds and only one warning is sent per low-battery episode.

After plugging in, the leftover single warning has to be dismissed by hand until upstream dismisses it on AC connect.

Verify

udevadm monitor --subsystem-match=power_supply stays quiet while the charger is connected, and draining past 10% produces exactly one "Time to recharge!" notification.

Sources

omarchy-low-battery-toast-storm-or-stuck-after-charging