[Bug 1934944] Re: power-profiles-daemon package conflicts with TLP
Bin Li
1934944 at bugs.launchpad.net
Mon Sep 6 07:10:41 UTC 2021
** Changed in: oem-priority
Assignee: (unassigned) => Bin Li (binli)
** Changed in: oem-priority
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to tlp in Ubuntu.
https://bugs.launchpad.net/bugs/1934944
Title:
power-profiles-daemon package conflicts with TLP
Status in OEM Priority Project:
Triaged
Status in tlp package in Ubuntu:
Confirmed
Bug description:
THE PROBLEM:
The new power-profiles-daemon package (installed by default in Ubuntu
21.04) comes with a systemd unit power-profiles-daemon.service. This
unit declares a conflict with tlp.service causing tlp.service to be
effectively disabled.
/lib/systemd/system/power-profiles-daemon.service (notice the Conflicts= directive)
--------------
[Unit]
Description=Power Profiles daemon
Conflicts=tuned.service tlp.service auto-cpufreq.service
Before=multi-user.target display-manager.target
...
--------------
If a unit has a Conflicts= directive on another unit, starting the
former will stop the latter and vice versa. And because tlp.service
doesn't declare Conflicts= directive on power-profiles-daemon.service,
it will always be the one that gets disabled during system startup
regardless of the activation order of the units.
An issue has been reported to the project maintainer regarding this
[1].
EXPECTED BEHAVIOUR:
TLP package is not installed by default. Installing TLP package
explicitly should make it the active power management agent in the
system. Any other power management agents installed in the system
should be effectively disabled including Power Profiles daemon.
ACTUAL BEHAVIOUR:
Even after installing TLP package explicitly. The power-profiles-
daemon.service unit will remain the active service causing tlp.service
to be effectively disabled. Although tlp.service unit is disabled, a
change in the power source will make TLP apply the desired settings.
This is the case because tlp.service is only responsible for applying
the TLP settings at boot [2][3].
PROPOSED SOLUTION:
TLP service unit may include Conflicts=power-profiles-daemon.service
directive. This will resolve the issue in the current setup of both
services, as tlp.service is activated before power-profiles-
daemon.service.
Also, configuring TLP service unit with Before=power-profiles-
daemon.service will make tlp.service activation always takes
precedence over power-profiles-daemon.service.
REFERENCES:
[1] https://github.com/linrunner/TLP/issues/564
[2] https://linrunner.de/tlp/introduction.html#how-it-works
[3] https://linrunner.de/tlp/developers/architecture.html
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: tlp 1.3.1-2
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 8 01:26:37 2021
InstallationDate: Installed on 2020-03-14 (480 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
PackageArchitecture: all
SourcePackage: tlp
UpgradeStatus: Upgraded to hirsute on 2021-06-03 (34 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934944/+subscriptions
More information about the foundations-bugs
mailing list