diff options
| author | Craig Jennings <c@cjennings.net> | 2026-08-16 04:58:44 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-08-16 04:58:44 -0500 |
| commit | 6dbc86df63a12b6ea16287bd1086b6aed545329b (patch) | |
| tree | 08c6f8e9801637577216b25519cd204df29a4724 /dotfiles/common | |
| parent | e8004e3a7416c57661d43e8bfaefb7c77255129e (diff) | |
| download | archsetup-6dbc86df63a12b6ea16287bd1086b6aed545329b.tar.gz archsetup-6dbc86df63a12b6ea16287bd1086b6aed545329b.zip | |
fix(installer): mask power-profiles-daemon so TLP survives on laptops
power-profiles-daemon.service declares Conflicts=tuned.service tlp.service auto-cpufreq.service, so systemd TERMs TLP the moment ppd starts. The line is in ppd's unit, not tlp's, so grepping tlp.service for it finds nothing.
Leaving ppd disabled was never enough. It ships D-Bus activation files, so the desktop-settings panel's own powerprofilesctl call starts it on demand. Velox ran that way from its rebuild on 2026-08-13 until today. TLP failed at every boot and none of its battery policy applied, while the machine looked correctly configured.
I mask and then stop. The mask closes the re-activation window, and the stop is what makes a repair re-run take effect, since a mask alone leaves a running ppd running.
I left desktops alone. They have no TLP to conflict with, and the panel's power control needs ppd there.
Diffstat (limited to 'dotfiles/common')
0 files changed, 0 insertions, 0 deletions