Debian

Install TLP on Ubuntu, Fedora, Debian: Profiles and PPD Conflict

To install TLP on a modern laptop distro, you first have to drop the power daemon your desktop already runs. The two won’t share a machine. On Ubuntu and Debian, apt quietly removes power-profiles-daemon the moment you install TLP. On Fedora, dnf refuses outright until you let it erase tuned and tuned-ppd. None of that is a bug, but it does surprise you if you expected TLP to sit on top of your existing setup.

Original content from computingforgeeks.com - post 189092

This guide gets TLP running on all three distros from the newest package each one offers and shows the exact conflict messages you’ll see. It then switches between the three profiles and moves your config to the renamed _PRF and _BAL settings that TLP 1.11 introduced. Built and run on Ubuntu 26.04.1 LTS, Debian 13 and Fedora 45 cloud VMs in November 2026, so every command and every warning below is a real capture. Those VMs had no battery, so charge thresholds and measured savings are out of scope, and the last section says exactly what that leaves untested.

Pick the Right TLP Package Source

The distro archives lag behind TLP releases, so on Ubuntu and Debian you’ll want the newer source in the third column. TLP 1.11.0 was tagged on 12 November 2026, but on that date no repository below shipped it yet. The table shows what each one offered when the lab ran.

DistroDefault archiveNewer sourceDaemon the install removes
Ubuntu 26.04 LTS1.8.0-1ubuntu21.10.2 from ppa:linrunner/tlppower-profiles-daemon (apt does it silently)
Debian 13 (trixie)1.8.0-11.10.2 from trixie-backportspower-profiles-daemon (apt does it silently)
Fedora 451.10.1-2.fc451.11 testing build in linrunner’s own repotuned and tuned-ppd (only with --allowerasing)

Ubuntu’s desktop image ships power-profiles-daemon (it’s in the 26.04.1 desktop manifest), and Fedora Workstation has used tuned-ppd as its profile daemon since Fedora 41. The cloud images in this lab had neither installed, so each conflict below was set up on purpose by installing the desktop daemon first. On a real laptop you’ll hit the same thing without trying.

Install TLP on Ubuntu from the PPA

Ubuntu’s own archive carries an older TLP that predates tlp-pd, the profile daemon that replaces power-profiles-daemon’s D-Bus API. The maintainer’s PPA carries the newest packaged build for 26.04, so add it first:

sudo add-apt-repository -y ppa:linrunner/tlp
sudo apt update

Check which version apt will now pick. You want the PPA build above the archive one.

apt-cache policy tlp

The candidate comes from ppa.launchpadcontent.net, which is what you want:

apt-cache policy tlp on Ubuntu 26.04 showing the linrunner PPA candidate 1.10.2 above the archive 1.8.0

If the candidate still reads 1.8.0-1ubuntu2, the PPA didn’t get added, and installing now would give you the old release without tlp-pd. Install TLP and the radio device wizard next:

sudo apt install -y tlp tlp-rdw

Read the transaction before it scrolls away. With power-profiles-daemon present, apt lists it under REMOVING and goes ahead without asking, because -y covers removals too:

sudo apt install tlp tlp-rdw on Ubuntu listing power-profiles-daemon under REMOVING and TLP version 1.10.2

That’s 33 packages in and one out on a minimal image. tlp-pd came in automatically, along with NetworkManager for tlp-rdw, so the GNOME and KDE power menus keep working after power-profiles-daemon is gone. If you install with --no-install-recommends, add tlp-pd to the line yourself, as linrunner’s install pages do. Now enable the service and apply the settings once:

sudo systemctl enable --now tlp.service
sudo tlp start
sudo tlp-stat -s

In the status block you should see tlp enabled with a recent last run, and tlp-pd running.

TLP started using profile performance/AC (auto).
--- TLP 1.10.2 --------------------------------------------

+++ System Info
System         = Google  Google Compute Engine
BIOS           = Google Google
OS release     = Ubuntu 26.04.1 LTS
Kernel         = 7.0.0-1017-gcp #19-Ubuntu SMP PREEMPT Wed Oct 28 19:54:07 UTC 2026 x86_64
Init system    = systemd 259
Boot mode      = UEFI
Suspend mode   = s2idle [deep]

+++ TLP Status
tlp            = enabled, last run: 10:30:22, 1 sec(s) ago
tlp-rdw        = enabled
tlp-pd         = enabled, running
TLP profile    = performance/AC
Power source   = unknown

Power source = unknown is the VM talking, since there’s no AC adapter or battery for TLP to read. On a laptop it says AC or battery, and the auto profile follows it. That’s it for Ubuntu. If you’re on 26.04 for the first time, the Resolute Raccoon feature rundown covers what else changed in the release.

Install TLP on Debian 13 from Backports

Debian 13 keeps the newer TLP in trixie-backports at pin priority 100, so a plain apt install tlp still picks the old trixie build. The GCP image already had backports in its sources. A desktop install usually doesn’t, so create a sources file for it the way linrunner’s Debian page does:

sudo vim /etc/apt/sources.list.d/debian-backports.sources

Paste these lines, which are linrunner’s example with the release name filled in. The lab VM never needed this file, so it wasn’t run there:

Types: deb deb-src
URIs: http://deb.debian.org/debian
Suites: trixie-backports
Components: main
Enabled: yes
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Run sudo apt update, then ask for the backports target explicitly:

sudo apt install -y -t trixie-backports tlp tlp-rdw

Debian behaves exactly like Ubuntu here. The summary pulls tlp-pd in as a recommended package and drops power-profiles-daemon.

REMOVING:
  power-profiles-daemon

Summary:
  Upgrading: 3, Installing: 43, Removing: 1, Not Upgrading: 16
  Download size: 11.9 MB
  Space needed: 44.8 MB / 17.8 GB available

Enable it the same way with sudo systemctl enable --now tlp.service and sudo tlp start. On the trixie VM, tlp-stat -s reported TLP 1.10.2 on kernel 6.12.116+deb13-cloud-amd64 with tlp, tlp-rdw and tlp-pd all enabled. If you also keep a list of everyday apt commands handy, the apt cheat sheet covers -t and pinning in more depth.

Install TLP on Fedora and Remove tuned-ppd

Fedora is the one distro where the conflict stops you instead of being resolved for you. The tlp package declares a conflict with tuned, and tuned-ppd needs tuned, so dnf will not touch either without permission. A plain install on a box with tuned-ppd returns this.

sudo dnf install -y tlp tlp-rdw

dnf prints both problems and the two flags it will accept.

dnf install tlp on Fedora 45 failing because installed tuned conflicts with tlp, with the allowerasing hint

Skip --skip-broken, because it would just skip TLP and leave tuned in place, which is the opposite of what you want. --allowerasing is the flag the linrunner Fedora install page uses too:

sudo dnf install -y --allowerasing tlp tlp-rdw

The transaction summary confirms the swap: tuned and tuned-ppd are the two removals, and tlp-pd arrives as a weak dependency. Any tuned config you’d edited survives as an .rpmsave file under /etc/tuned/:

Installing weak dependencies:
 perl-NDBM_File         x86_64 0:1.18-527.fc45      fedora      28.3 KiB
 smartmontools          x86_64 1:7.5-11.fc45        updates      2.4 MiB
 tlp-pd                 noarch 0:1.10.1-2.fc45      fedora      59.0 KiB

Transaction Summary:
 Installing:        78 packages
 Removing:           2 packages

Fedora’s presets don’t enable tlp.service or tlp-pd.service, so you turn TLP on yourself and then look at the status.

sudo systemctl enable --now tlp.service
sudo tlp start
sudo tlp-stat -s

TLP starts, but tlp-stat prints an error you should not ignore.

+++ TLP Status
tlp            = enabled, last run: 10:30:21 AM, 0 sec(s) ago
tlp-rdw        = enabled
tlp-pd         = disabled, running
TLP profile    = performance/AC
Power source   = unknown

Error: After the next restart, you won't be able to switch TLP profiles by mouse click because tlp-pd.service is not enabled --> Run 'systemctl enable tlp-pd.service' to ensure the full functionality of TLP.

Ubuntu and Debian enabled tlp-pd during the install, so this one is Fedora only.

Error: “tlp-pd.service is not enabled”

tlp-pd is running in this session, but the unit is disabled, so nothing starts it at boot. After a reboot, the GNOME or KDE power profile switch would have nothing to talk to. Enable it so it starts with the graphical target:

sudo systemctl enable --now tlp-pd

systemd confirms the link, and the error is gone from the next tlp-stat -s:

Created symlink '/etc/systemd/system/graphical.target.wants/tlp-pd.service' → '/usr/lib/systemd/system/tlp-pd.service'.

The Fedora 45 VM ran SELinux enforcing the whole time, and TLP didn’t need any policy change. linrunner’s page also has you mask systemd-rfkill.service and systemd-rfkill.socket so tlp-rdw owns radio state on boot. That step wasn’t run on the VM, which has no radios to manage, but you should do it on a laptop with Wi-Fi and Bluetooth. If you’re setting up a fresh Fedora laptop anyway, pair this with RPM Fusion and the multimedia codecs.

Fix the power-profiles-daemon Conflict

TLP and power-profiles-daemon both write CPU energy policy and platform profile at boot, so whichever runs last wins and the other one’s settings vanish. The packages declare a mutual conflict for that reason, and the TLP FAQ on power-profiles-daemon says to run only one. You’ll usually meet it in one of three ways:

  1. Installing TLP removes power-profiles-daemon, which is the normal case shown above.
  2. Installing power-profiles-daemon later removes TLP. On Debian, apt install power-profiles-daemon listed tlp tlp-pd tlp-rdw under REMOVING.
  3. Both end up on disk, through a forced dpkg install or a leftover unit, and both try to start.

The third case is the one that hides. To see what TLP reports there, the Debian lab forced both packages in with dpkg -i --force-conflicts and started power-profiles-daemon:

sudo systemctl start power-profiles-daemon
sudo tlp-stat -s

tlp-stat opens with the warning and closes with the fix, and the TLP profile drops to unknown.

tlp-stat -s warning that TLP power saving will not apply on boot because power-profiles-daemon.service is active

Don’t rely on tlp-stat -w to catch this, because on the same box it printed No warnings detected. The warning only shows in the status section. Mask the unit so nothing can start it again:

sudo systemctl mask --now power-profiles-daemon.service
sudo systemctl enable --now tlp.service
systemctl is-active power-profiles-daemon tlp

The mask points the unit at /dev/null, power-profiles-daemon reports inactive, and TLP is active again.

Created symlink '/etc/systemd/system/power-profiles-daemon.service' → '/dev/null'.
Synchronizing state of tlp.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable tlp
inactive
active

The next tlp-stat -s showed the profile back at performance/AC with no warning line. Masking is the quick fix, but removing the package is cleaner. A forced install also leaves apt in a broken state that you will trip over on the next upgrade. apt still sees two packages that declare a conflict with each other, and it refuses every later install until one of them goes.

Error: “power-profiles-daemon : Conflicts: tlp”

On the Debian VM, the next install after the forced one failed straight away. Adding tlp-pd from backports gave this.

Unsatisfied dependencies:
 power-profiles-daemon : Conflicts: tlp but 1.10.2-2~bpo13+1 is to be installed
 tlp-pd : Conflicts: power-profiles-daemon
Error: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

Remove power-profiles-daemon, then install the TLP set again and enable both services:

sudo apt remove -y power-profiles-daemon
sudo apt install -y -t trixie-backports tlp tlp-rdw tlp-pd
sudo systemctl enable --now tlp.service tlp-pd.service

That cleared it on the trixie VM: tlp and tlp-pd active, power-profiles-daemon inactive and still masked, with only its config left behind (rc in dpkg -l). apt purge power-profiles-daemon clears that too if you want it gone.

Switch Between TLP Profiles

TLP has three profiles, and in auto mode it picks performance on AC and balanced on battery. You can override that from the shell:

  1. sudo tlp performance, sudo tlp balanced or sudo tlp power-saver picks a profile by name.
  2. sudo tlp ac and sudo tlp bat force the AC or battery profile, marked (manual) in the output.
  3. sudo tlp start goes back to auto.

tlp-pd also ships tlpctl, which talks to the same D-Bus API the desktop uses. Here’s a manual switch followed by tlpctl list on the Ubuntu VM:

sudo tlp power-saver
sudo tlp ac
tlpctl list

Each switch prints the profile it applied, and tlpctl list marks the active one with an asterisk.

sudo tlp power-saver and tlp ac switching profiles, then tlpctl list showing performance, balanced and power-saver

CpuDriver : tlp and PlatformDriver : tlp mean tlp-pd is answering for both, the way power-profiles-daemon used to. powerprofilesctl is not installed anymore, so tlpctl is the command to use. One snag showed up on all three distros: tlpctl set power-saver run as a normal user over SSH failed with this error:

Error: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.Failed: Unable to set property org.freedesktop.UPower.PowerProfiles.ActiveProfile (0)

The tlp-pd journal (journalctl -u tlp-pd) gives the real reason, Not authorized to switch profile. polkit refused the change from a remote session, so over SSH you’ll need sudo tlp power-saver instead. From the GNOME or KDE power menu on the laptop itself, the switch goes through tlp-pd as normal.

Move Your Config to the TLP 1.11 Names

TLP 1.11 renames the profile suffixes in every setting so they match the profile names you just switched between. Old names still work because TLP translates them when it reads the config, but tlp-stat nags about each one. The 1.11.0 release notes and the beta entries in the TLP changelog list the changes that matter for an existing /etc/tlp.conf:

  • _AC becomes _PRF and _BAT becomes _BAL, so CPU_BOOST_ON_BAT is now CPU_BOOST_ON_BAL. _SAV stays.
  • More settings get a _SAV variant, including SOUND_POWER_SAVE_ON_SAV, SATA_LINKPWR_ON_SAV and MEM_SLEEP_ON_SAV.
  • PLATFORM_PROFILE_ON_* now takes a space-separated fallback list, and RADEON_DPM_STATE is gone.

Don’t rename anything while your distro still ships the 1.10 line. Those releases don’t know _PRF or _BAL, so renamed settings would just be ignored. Leave the old names in place and they’ll keep working after the upgrade.

To see the rename in action before the repos catch up, the Fedora 45 VM used linrunner’s own RPM repository, whose testing channel carried 1.11.0-beta.2 on release day. Only bug fixes went into 1.11.0 after that beta, so the config behaviour matches. Treat this as a preview, not the install path for a daily laptop:

sudo dnf install -y "https://repo.linrunner.de/fedora/tlp/repos/releases/tlp-release.fc$(rpm -E %fedora).noarch.rpm"
sudo dnf --enablerepo=tlp-updates-testing install -y --allowerasing tlp tlp-pd tlp-rdw
rpm -q tlp tlp-pd tlp-rdw
tlp --version

dnf noted that it skipped the OpenPGP check for the release RPM, since it came from a URL, and the testing build landed:

tlp-1.11.0-beta.2.fc45.noarch
tlp-pd-1.11.0-beta.2.fc45.noarch
tlp-rdw-1.11.0-beta.2.fc45.noarch
TLP version 1.11.0-beta.2

tlp-pd from that beta didn’t start on the minimal cloud image. Its journal ended in ModuleNotFoundError: No module named 'gi' and systemd gave up with start-limit-hit, so check systemctl status tlp-pd if you try it. The missing module is Python’s GObject binding (python3-gobject on Fedora), though adding it wasn’t tested here. If it stays failed on a laptop, sudo systemctl disable --now tlp-pd stops the restart loop and you lose desktop profile switching until a fixed build lands. tlp itself was unaffected. The release RPM also leaves linrunner’s repos enabled. When you’re done previewing, sudo dnf remove tlp-release deletes those repo files, and sudo dnf distro-sync tlp tlp-pd tlp-rdw then moves you back to Fedora’s own build. Without that second command the beta stays, because it outranks Fedora’s version number. Next, create a drop-in with settings in the old naming, the kind of file you probably carry from an older install.

sudo vim /etc/tlp.d/50-legacy.conf

This is the exact file the lab used.

CPU_ENERGY_PERF_POLICY_ON_AC=performance
CPU_ENERGY_PERF_POLICY_ON_BAT=power
PLATFORM_PROFILE_ON_AC=performance
PLATFORM_PROFILE_ON_BAT=low-power
CPU_BOOST_ON_BAT=0
WIFI_PWR_ON_BAT=off

Apply it and ask tlp-stat for only the settings that differ from the defaults:

sudo tlp start
sudo tlp-stat --cdiff

Every legacy line comes back under its new name with a Runtime-translated note, and the start message now says performance/PRF.

tlp-stat --cdiff on TLP 1.11 showing legacy _ON_AC and _ON_BAT settings runtime-translated to _ON_PRF and _ON_BAL

That list is your to-do list, with file and line number for each setting. Read every note before touching the file, because some old names change their base name too. CPU_HWP_ON_AC and CPU_HWP_ON_BAT are the dangerous pair: they become CPU_ENERGY_PERF_POLICY_ON_PRF and _ON_BAL, so rename them by hand first. A blind suffix swap would turn them into CPU_HWP_ON_PRF, a name TLP 1.11 doesn’t know. tlp-stat still lists it with no note, so it looks fine, but TLP ignores the setting. One name goes wrong the other way: RESTORE_THRESHOLDS_ON_BAT keeps its old suffix in 1.11, so leave that line out of the swap. Also note that --cdiff hides any line whose value matches the default, and plain sudo tlp-stat -c shows the full list.

Once only plain _ON_AC and _ON_BAT lines are left, as in this drop-in, sed handles the rest of the file in one go:

sudo sed -i -e 's/_ON_AC=/_ON_PRF=/' -e 's/_ON_BAT=/_ON_BAL=/' /etc/tlp.d/50-legacy.conf
sudo tlp start
sudo tlp-stat --cdiff

The same six settings now print with no translation notes.

TLP started using profile performance/PRF (auto).
--- TLP 1.11.0-beta.2 --------------------------------------------

+++ Configured Settings (only differences to defaults):
/etc/tlp.d/50-legacy.conf L0001: CPU_ENERGY_PERF_POLICY_ON_PRF="performance"
/etc/tlp.d/50-legacy.conf L0002: CPU_ENERGY_PERF_POLICY_ON_BAL="power"
/etc/tlp.d/50-legacy.conf L0003: PLATFORM_PROFILE_ON_PRF="performance"
/etc/tlp.d/50-legacy.conf L0004: PLATFORM_PROFILE_ON_BAL="low-power"
/etc/tlp.d/50-legacy.conf L0006: WIFI_PWR_ON_BAL="off"
/etc/tlp.d/50-legacy.conf L0005: CPU_BOOST_ON_BAL="0"

On your own config, run --cdiff once more after the edit. Any line that still carries a note, such as USB_WHITELIST, which the sed doesn’t touch, needs a hand fix. Then make sure grep -nE 'CPU_HWP_ON_|RESTORE_THRESHOLDS_ON_BAL' /etc/tlp.conf /etc/tlp.d/*.conf prints nothing, since --cdiff flags neither mistake. Rename any RESTORE_THRESHOLDS_ON_BAL hit back to _ON_BAT. sudo tlp power-saver on this build reported power-saver/SAV, so the third profile kept its name.

Check What a VM Can’t Show

Battery care is where TLP earns its keep on a ThinkPad or a Framework, and none of it can run on a VM. tlp-stat -b makes that clear on the Debian box:

sudo tlp-stat -b

The generic plugin with no supported features is what you get without a battery or a vendor ACPI driver.

sudo tlp-stat -b on a cloud VM reporting plugin generic, no supported features and no batteries detected

So charge thresholds (START_CHARGE_THRESH_BAT0 and friends), the Lenovo charge_types fix in 1.11 and battery recalibration weren’t tested here. Neither was platform_profile, because /sys/firmware/acpi/platform_profile does not exist on these VMs, and no power draw was measured. On real hardware, sudo tlp-stat -b names the plugin your laptop gets, and TLP’s battery care vendor specifics list which makers support thresholds. If you’re still choosing the hardware, the Linux laptops for developers roundup covers which ones run Linux well. Running CachyOS on that laptop? The post-install CachyOS guide covers the rest of the first-boot setup.

Roll Back to the Stock Daemon

If TLP isn’t for you, put the distro default back. Order matters on Ubuntu and Debian, because a masked power-profiles-daemon stays masked after reinstalling and won’t start:

sudo systemctl disable --now tlp.service tlp-pd.service
sudo apt purge -y tlp tlp-rdw tlp-pd
sudo systemctl unmask power-profiles-daemon.service
sudo apt install -y power-profiles-daemon
powerprofilesctl get

On the Ubuntu VM, power-profiles-daemon came back active and powerprofilesctl get printed balanced. Fedora needs tuned and tuned-ppd reinstalled and enabled:

sudo dnf remove -y tlp tlp-rdw
sudo dnf install -y tuned-ppd
sudo systemctl enable --now tuned tuned-ppd
tuned-adm active

Both services came back active, and tuned-adm active printed Current active profile: balanced. From there, tuned’s own profiles are the knob to turn, and the tuned-adm guide walks through them.

Keep reading

How to Upgrade Fedora 44 to Fedora 45 (GUI, CLI and Rollback) Fedora How to Upgrade Fedora 44 to Fedora 45 (GUI, CLI and Rollback) Upgrade Ubuntu 24.04 to Ubuntu 26.04 LTS (Step by Step) Ubuntu Upgrade Ubuntu 24.04 to Ubuntu 26.04 LTS (Step by Step) UFW Firewall Commands with Examples on Ubuntu 26.04 / 24.04 Security UFW Firewall Commands with Examples on Ubuntu 26.04 / 24.04 Deploy Collabora Online Office on Ubuntu with Let’s Encrypt SSL Cloud Deploy Collabora Online Office on Ubuntu with Let’s Encrypt SSL Install CyberPanel on Ubuntu 26.04 / 24.04 with Let’s Encrypt Ubuntu Install CyberPanel on Ubuntu 26.04 / 24.04 with Let’s Encrypt How To Install MySQL 8.0 on Ubuntu 24.04|22.04|20.04 Databases How To Install MySQL 8.0 on Ubuntu 24.04|22.04|20.04

Leave a Comment

Press ESC to close