Make Power Saver stick when switching straight from Performance
Issue #14174 (open, 2026-10-03, Dell XPS 14 DA14260, ppd 0.30-1) supports the symptom, the two non-overlapping platform-profile handlers, platform_profile_choices showing balanced performance, the reproduction with plain powerprofilesctl, and the go-through-Balanced workaround. The installed omarchy-powerprofiles-set confirms it saves the requested profile, not the one the daemon ends on. The defect is the last block. omarchy-powerprofiles-set applies each profile as it saves it, so ac balanced then battery power-saver leaves a reader on AC running Power Saver until the next plug event. The corrected fix finishes with autodetect, which applies the right one. The step from Balanced to Power Saver is the case the reporter found sticks. Not exercised: this machine is not affected hardware. Second audit confirmed the corrected text: Issue #14174 (open, Dell XPS 14 DA14260, ppd 0.30-1) supports the symptom, both non-overlapping platform-profile handlers, platform_profile_choices = balanced performance, the plain-powerprofilesctl reproduction and the go-through-Balanced workaround. The cause keeps the reporter's 'seems' on the daemon mechanism. omarchy-powerprofiles-set (identical on quattro) saves the requested profile and applies it immediately. Traced the final block: on AC it ends on balanced, on battery on power-saver, and every Power Saver switch in it starts from Balanced, the case the reporter found sticks. An unplug then goes balanced to power-saver, which also sticks. /sys/class/platform-profile/*/{name,choices} is the kernel platform-profile class the issue's output comes from. Not exercised: this machine is not affected hardware.
Symptom
When I pick Power Saver while on Performance, the panel jumps to Balanced a moment later. powerprofilesctl get prints balanced but ~/.local/state/omarchy/powerprofiles/battery says power-saver, and after unplugging the laptop runs Balanced instead of Power Saver. Going Balanced to Power Saver works fine. Seen on a Dell XPS 14 (Panther Lake).
Cause
A power-profiles-daemon 0.30 behaviour, reproducible with plain powerprofilesctl set performance followed by powerprofilesctl set power-saver. The machine registers two platform-profile handlers whose choices do not overlap below balanced, so /sys/firmware/acpi/platform_profile_choices shows only balanced performance. With no low-power choice, the daemon writes balanced to the firmware for Power Saver. Coming from Performance that is a real firmware change, and the daemon appears to take the firmware's change notification as a new user choice of Balanced. omarchy-powerprofiles-set saves the profile requested, not the one the daemon ends on.
Fix
Check whether your machine has the non-overlapping handlers:
cat /sys/firmware/acpi/platform_profile_choices
grep -H . /sys/class/platform-profile/*/name /sys/class/platform-profile/*/choices 2>/dev/null
Workaround: go through Balanced first. This sticks every time in the reporter's tests:
powerprofilesctl set balanced
powerprofilesctl set power-saver
powerprofilesctl get
In the Omarchy UI, pick Balanced before Power Saver. The automatic restore on unplug can still bounce if your AC profile is performance, so save balanced for AC. omarchy-powerprofiles-set applies each profile as it saves it, so finish with autodetect to land on the right one for the current power source:
omarchy-powerprofiles-set ac balanced
omarchy-powerprofiles-set battery power-saver
omarchy-powerprofiles-set autodetect
powerprofilesctl get
Verify
Unplug the charger. Two seconds later powerprofilesctl get should still print power-saver.