$ apt-cache policy cpupower-gui
cpupower-gui:
Installed: 1.0.0-6ubuntu0.26.04.1
Candidate: 1.0.0-6ubuntu0.26.04.1
Version table:
*** 1.0.0-6ubuntu0.26.04.1 100
100 https://mirrors.vcea.wsu.edu/ubuntu resolute-proposed/universe
amd64 Packages
100 /var/lib/dpkg/status
1.0.0-6 500
500 https://mirrors.vcea.wsu.edu/ubuntu resolute/universe amd64 Packages
(Yes, I'm using the Washington State University mirror. My wife
graduated from their rival so I feel dirty.)
The good news is that the systemd service now runs properly at boot.
$ sudo systemctl status cpupower-gui.service
○ cpupower-gui.service - Apply cpupower-gui config at boot
Loaded: loaded (/usr/lib/systemd/system/cpupower-gui.service; enabled;
preset: enabled)
Active: inactive (dead) since Sun 2026-09-06 15:38:25 PDT; 8s ago
Invocation: cad39e4eae8c4c2689d706a08529a7f5
Docs: https://github.com/vagnum08/cpupower-gui
man:cpupower-gui(1)
Process: 261374 ExecStart=/usr/bin/cpupower-gui config -a (code=exited,
status=0/SUCCESS)
Main PID: 261374 (code=exited, status=0/SUCCESS)
Mem peak: 13.9M
CPU: 83ms
Sep 06 15:38:25 erich-UbuntuStudioMain cpupower-gui[261374]: Minimum
Frequency: 800.0 MHz, Maximum Frequency: 3600.0 MHz
Sep 06 15:38:25 erich-UbuntuStudioMain cpupower-gui[261374]: Governor:
Powersave, Online: True
Sep 06 15:38:25 erich-UbuntuStudioMain cpupower-gui[261374]: Setting CPU: 14
Sep 06 15:38:25 erich-UbuntuStudioMain cpupower-gui[261374]: Minimum
Frequency: 800.0 MHz, Maximum Frequency: 3600.0 MHz
Sep 06 15:38:25 erich-UbuntuStudioMain cpupower-gui[261374]: Governor:
Powersave, Online: True
Sep 06 15:38:25 erich-UbuntuStudioMain cpupower-gui[261374]: Setting CPU: 15
Sep 06 15:38:25 erich-UbuntuStudioMain cpupower-gui[261374]: Minimum
Frequency: 800.0 MHz, Maximum Frequency: 3600.0 MHz
Sep 06 15:38:25 erich-UbuntuStudioMain cpupower-gui[261374]: Governor:
Powersave, Online: True
Sep 06 15:38:25 erich-UbuntuStudioMain systemd[1]: cpupower-gui.service:
Deactivated successfully.
Sep 06 15:38:25 erich-UbuntuStudioMain systemd[1]: Finished
cpupower-gui.service - Apply cpupower-gui config at boot.
The bad news is that this fix is only half-done because anything done at
the system level gets overridden as soon as the user logs-in:
$ systemctl --user status cpupower-gui-user
× cpupower-gui-user.service - Apply cpupower-gui config at user login
Loaded: loaded (/usr/lib/systemd/user/cpupower-gui-user.service; enabled;
preset: enabled)
Active: failed (Result: exit-code) since Sun 2026-09-06 15:40:25 PDT; 13s
ago
Invocation: 8fb7f2871a8d4321b780b51a0c5dc703
Process: 262009 ExecStart=/usr/bin/cpupower-gui config (code=exited,
status=1/FAILURE)
Main PID: 262009 (code=exited, status=1/FAILURE)
Mem peak: 28.7M
CPU: 184ms
Sep 06 15:40:24 erich-UbuntuStudioMain systemd[5036]: Starting
cpupower-gui-user.service - Apply cpupower-gui config at user lo>
Sep 06 15:40:25 erich-UbuntuStudioMain cpupower-gui[262009]: unable to open
file '/etc/dconf/db/site': Failed to open file “/et>
Sep 06 15:40:25 erich-UbuntuStudioMain cpupower-gui[262009]: This application
can not open files.
Sep 06 15:40:25 erich-UbuntuStudioMain systemd[5036]:
cpupower-gui-user.service: Main process exited, code=exited, status=1/FAI>
Sep 06 15:40:25 erich-UbuntuStudioMain systemd[5036]:
cpupower-gui-user.service: Failed with result 'exit-code'.
Sep 06 15:40:25 erich-UbuntuStudioMain systemd[5036]: Failed to start
cpupower-gui-user.service - Apply cpupower-gui config at
With that, the initial complaint is fixed, but this should probably be
continued. I'm marking as verification-failed and will be uploading
another fix.
** Changed in: cpupower-gui (Ubuntu Stonking)
Status: Fix Released => In Progress
** Changed in: cpupower-gui (Ubuntu Stonking)
Status: In Progress => Triaged
** Changed in: cpupower-gui (Ubuntu Stonking)
Status: Triaged => In Progress
** Changed in: cpupower-gui (Ubuntu Resolute)
Status: Fix Committed => Triaged
** Changed in: cpupower-gui (Ubuntu Stonking)
Importance: Medium => High
** Tags removed: verification-needed-resolute
** Tags added: verification-failed-resolute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2151790
Title:
Failed to start cpupower-gui.service - Apply cpupower-gui config at
boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpupower-gui/+bug/2151790/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
