Resolve TLP and power-profiles-daemon fighting over the same knobs
Checked on this Omarchy 4.0.2-1 workstation on 2026-09-12 and against TLP's ppd FAQ, the Arch TLP and CPU frequency scaling wiki pages, the Arch package data for tlp and tlp-pd, and omacom/omarchy issue 8596. What held: the two warning strings in the symptom are verbatim from the TLP FAQ for 1.6-and-later and 1.5, the shared tunables and the overwriting are stated there, and systemctl show power-profiles-daemon.service -p Conflicts on this machine returns tuned.service shutdown.target system76-power.service tlp.service auto-cpufreq.service, confirming the Conflicts claim locally. What was wrong is the Omarchy framing and the tlp-pd advice. Omarchy 4 installs power-profiles-daemon 0.30-1 from install/omarchy-base.packages and enables it in install/config/enable-services.sh, and it never installs TLP: the only tlp match in /usr/share/omarchy and in the whole quattro tree is the substring inside hyprctlProc in shell/Commons/Style.qml, so the record was reading as an Omarchy default when it is a user-added package. The real defect is the fix's pacman -S tlp-pd line: tlp-pd 1.10.2 declares conflicts=power-profiles-daemon and provides=power-profiles-daemon and ships only /usr/bin/tlp-pd, /usr/bin/tlpctl and the two D-Bus service files, so installing it removes /usr/bin/powerprofilesctl, which pacman -Qo confirms is owned by power-profiles-daemon 0.30-1, while omarchy-powerprofiles-list, omarchy-powerprofiles-set and shell/plugins/menu/Menu.qml line 277 all invoke powerprofilesctl by name. On Omarchy the record's recommended TLP branch therefore breaks the exact UI it claims to preserve. The danger was also overstated: issue 8596 is still open and a contributor comment on it reproduces the crash with power-profiles-daemon active, enabled and healthy and no TLP, and the unconditional two-second powerprofilesctl get poll that comment blames is no longer in shell/plugins/services/battery/Service.qml on 4.0.2-1. I also confirmed the ALPM guard does not block these commands: /usr/bin/omarchy-update-pacman-guard aborts only when both a sync and a sysupgrade flag are on the pacman command line. Frequency lowered from very-common to common because on this corpus's primary target the problem cannot occur until the user installs TLP by hand. NOT exercised: I did not mask power-profiles-daemon, install tlp or tlp-pd, or start or stop any unit on this workstation, so the resulting menu breakage is reasoned from the package file lists and the Omarchy scripts rather than observed.
Masking power-profiles-daemon leaves GNOME, KDE and Omarchy's power menu with no profile source. On Omarchy 4, installing tlp-pd does not repair that, it breaks the menu a second way by removing /usr/bin/powerprofilesctl. Omarchy issue 8596 reports powerprofilesctl aborting rather than failing cleanly when the daemon is masked, but that issue is open and a contributor comment on it reproduces the same interpreter teardown crash with power-profiles-daemon active, enabled and unmasked and no TLP installed, so masking widens the window rather than being the cause.
Symptom
I installed TLP for better battery life and now settings randomly revert, or the desktop's power-profile switcher does nothing. tlp-stat prints: Warning: PLATFORM_PROFILE_ON_AC/BAT is not set because power-profiles-daemon is running. (TLP 1.5 said: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.)
Cause
TLP and power-profiles-daemon change some of the same kernel tunables, including the platform profile, the CPU energy performance preference, PCIe ASPM and USB autosuspend, and they overwrite each other's tuning. power-profiles-daemon.service declares a Conflicts= line that names TLP, read on this machine on 2026-09-12:
$ systemctl show power-profiles-daemon.service -p Conflicts
Conflicts=tuned.service shutdown.target system76-power.service tlp.service auto-cpufreq.service
A systemd Conflicts= only stops both units running at once. It does not stop both packages being installed. On Arch the tlp package conflicts with tuned and not with power-profiles-daemon, so the two install side by side and resolving the conflict is left to you.
This is never Omarchy 4's default state. Omarchy installs power-profiles-daemon from /usr/share/omarchy/install/omarchy-base.packages and enables it in /usr/share/omarchy/install/config/enable-services.sh, and TLP appears nowhere in /usr/share/omarchy or in the upstream omacom/omarchy quattro tree. TLP on an Omarchy box is something you added.
Fix
Pick one. On Omarchy 4 the answer is almost always power-profiles-daemon.
**Keeping power-profiles-daemon (what Omarchy 4 ships, and what its power menu drives):**
sudo systemctl disable --now tlp.service
sudo systemctl unmask power-profiles-daemon.service
sudo systemctl enable --now power-profiles-daemon.service
Removing the package is cleaner than leaving a disabled unit behind, and it is what TLP's own FAQ prefers:
sudo pacman -Rns tlp tlp-rdw
**Keeping TLP (plain Arch, and on Omarchy it costs you the power menu):**
sudo systemctl stop power-profiles-daemon.service
sudo systemctl mask power-profiles-daemon.service
sudo systemctl enable --now tlp.service
sudo systemctl mask systemd-rfkill.service systemd-rfkill.socket
Masking systemd-rfkill is the Arch wiki's instruction on the TLP page, because it implements the same radio state save and restore that TLP does.
To keep a power-profile switcher in GNOME, KDE or Cinnamon, install TLP's D-Bus compatibility layer, which has existed since TLP 1.9:
sudo pacman -S tlp-pd
**Do not do that on Omarchy 4.** tlp-pd 1.10.2 carries conflicts=power-profiles-daemon and provides=power-profiles-daemon, so pacman removes power-profiles-daemon in order to install it, and /usr/bin/powerprofilesctl goes with it. tlp-pd ships only /usr/bin/tlp-pd, /usr/bin/tlpctl and two D-Bus service files. Omarchy's power UI does not speak that D-Bus API directly, it shells out to powerprofilesctl by name:
/usr/share/omarchy/bin/omarchy-powerprofiles-list powerprofilesctl list
/usr/share/omarchy/bin/omarchy-powerprofiles-set powerprofilesctl set "$profile"
/usr/share/omarchy/shell/plugins/menu/Menu.qml:277 powerprofilesctl get
Omarchy's menu and power panel then show an empty profile list. Install tlp-pd only if you accept losing that menu.
Do not run tuned or tuned-ppd alongside either one. Both are named in the same Conflicts= line.
Omarchy's ALPM guard does not block any pacman command above. /usr/bin/omarchy-update-pacman-guard aborts only when the pacman command line carries both a sync flag and a sysupgrade flag, so pacman -S and pacman -Rns pass through it. Never turn one of them into pacman -Sy <pkg>, which is a partial upgrade.
Verify
systemctl is-active tlp power-profiles-daemon shows exactly one of the two active. With TLP running, sudo tlp-stat -s prints no conflict warning. With power-profiles-daemon running, powerprofilesctl lists the profiles and exits 0. On Omarchy 4, also check the command the menu actually calls:
omarchy-powerprofiles-list
Empty output means the power menu is broken even when the D-Bus API answers.