Lost the Gnome 41.1 settings for power management

Hello, I currently have on my Lenovo Yoga Slim 7 after updating from Fedora 35 to the current version, in Gnome 41.1 lost the settings for power management of the laptop.

System:
  Host: fedora Kernel: 5.15.4-201.fc35.x86_64 x86_64 bits: 64
  Desktop: GNOME 41.1 Distro: Fedora release 35 (Thirty Five)
Machine:
  Type: Laptop System: LENOVO product: 82A2 v: Yoga Slim 7 14ARE05

The settings have disappeared from the system settings.
I must confess that I have no idea how this could happen or how to solve this problem.
Many greetings

3 Likes

Check the output:

sudo powerprofilesctl list; \
rpm -q power-profiles-daemon; \
systemctl status power-profiles-daemon.service

Good morning and thank you for your reply.
The output from

gives an error

Couldn't get Profiles:  <class 'ReferenceError'>
Traceback (most recent call last):
  File "/usr/bin/powerprofilesctl", line 124, in get_profiles_property
    profiles = proxy.Get('(ss)', 'net.hadess.PowerProfiles', prop)
  File "/usr/lib/python3.10/site-packages/gi/overrides/Gio.py", line 349, in __call__
    result = self.dbus_proxy.call_sync(self.method_name, arg_variant,
gi.repository.GLib.Error: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer. (3)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/powerprofilesctl", line 132, in _list
    profiles = get_profiles_property('Profiles')
  File "/usr/bin/powerprofilesctl", line 126, in get_profiles_property
    raise ReferenceError
ReferenceError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/powerprofilesctl", line 262, in <module>
    main()
  File "/usr/bin/powerprofilesctl", line 218, in main
    _list()
  File "/usr/bin/powerprofilesctl", line 138, in _list
    raise SystemError
SystemError
power-profiles-daemon-0.10.1-2.fc35.x86_64
○ power-profiles-daemon.service
     Loaded: masked (Reason: Unit power-profiles-daemon.service is masked.)
     Active: inactive (dead)

1 Like
sudo systemctl unmask power-profiles-daemon.service
sudo systemctl restart power-profiles-daemon.service

Couldn't get Profiles (Fedora 35 update) (#58) · Issues · Bastien Nocera / power-profiles-daemon

3 Likes

You are my hero.
Thank you for your help and I admit that I am overwhelmed to realize what happened here and why the error occurred. Why was the service masked?
I just updated the system via Gnome software and from that moment the setting was gone.
I will look for the syntax related to the “mask & unmasked” command.

Once again many many thanks :grinning: :+1:
it works

this is great to read, I am not alone :+1: :grinning:

4 Likes

I have to report again, because the problem is not quite solved yet. The settings are available again, but an error message appears periodically in the logs.

Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
>>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!

Try resetting the config:

sudo rm -f /var/lib/power-profiles-daemon/*
sudo systemctl restart power-profiles-daemon.service
sudo powerprofilesctl list
1 Like

Thank you for your help

this is the result

 performance:
    Driver:     platform_profile
    Degraded:   no

* balanced:
    Driver:     platform_profile

  power-saver:
    Driver:     platform_profile

Once again many many thanks :grinning: :+1:

1 Like

The problem has unfortunately returned

16:38:22 tlp: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
16:38:22 tlp: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
16:38:22 tlp: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
16:38:21 tlp: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
16:38:21 tlp: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
[xxxxxx@fedora ~]$  systemctl status power-profiles-daemon.service
● power-profiles-daemon.service - Power Profiles daemon
     Loaded: loaded (/usr/lib/systemd/system/power-profiles-daemon.service; ena>
     Active: active (running) since Sun 2021-11-28 16:37:09 CET; 7min ago
   Main PID: 1071 (power-profiles-)
      Tasks: 3 (limit: 18361)
     Memory: 1.3M
        CPU: 71ms
     CGroup: /system.slice/power-profiles-daemon.service
             └─1071 /usr/libexec/power-profiles-daemon

Nov 28 16:37:09 fedora systemd[1]: Starting Power Profiles daemon...
Nov 28 16:37:09 fedora systemd[1]: Started Power Profiles daemon.
lines 1-12/12 (END)

[XXXXX@fedora ~]$ sudo powerprofilesctl list
[sudo] Passwort für XXXXX: 
  performance:
    Driver:     platform_profile
    Degraded:   no

* balanced:
    Driver:     platform_profile

  power-saver:
    Driver:     platform_profile

I would be happy if I could report better news

many greetings

Looks like power-profiles-daemon conflicts with tlp:

sudo dnf remove tlp
1 Like

Thanks again for that and now it should work.
But for me as a layman, the question is whether removing TLP is not a problem in the operation of my laptop in terms of battery? Is this application not necessary. especially since I do not know when it was installed and possibly still from Fedora34?
Thanks again for your help

via DeepL
I found an information about it.
https://linrunner.de/tlp/installation/fedora.html
The question only what you should really use? :dizzy_face:

1 Like

In any case, you can only use one of them.
Fedora and GNOME decided to integrate with power-profiles-daemon:
Changes/Power Profiles Daemon - Fedora Project Wiki
It should be fine to follow, unless you have a specific reason against it.

2 Likes

Thank you very much for the reply.
I would just like to mention that I did not install TLP and can only assume that this is left over from Fedora34 and I can’t figure out how it got into the system.

many greetings

1 Like