Cpupower-gui failing to launch

Development
1

Hi, this machine is operating openSUSE Tumbleweed 20240418, Plasma 6.0.4, QT 6.7.0 and KDE Framworks 6.1.0 .

I updated the machines snapshot, powercycled and discovered that cpupower-gui no longer launches from Application Menu > Settings > cpupower-gui

Thinkcentre-M57p:~> systemctl status cpupower-gui
× cpupower-gui.service - Apply cpupower-gui config at boot
    Loaded: loaded (/usr/lib/systemd/system/cpupower-gui.service; enabled; preset: disabled)
    Active: failed (Result: exit-code) since Fri 2024-04-19 14:13:09 CDT; 52min ago
      Docs: https://github.com/vagnum08/cpupower-gui
            man:cpupower-gui(1)
   Process: 3417 ExecStart=/usr/bin/cpupower-gui config (code=exited, status=1/FAILURE)
  Main PID: 3417 (code=exited, status=1/FAILURE)
       CPU: 118ms

Apr 19 14:13:09 Thinkcentre-M57p cpupower-gui[3417]:   File "/usr/lib/python3.11/site-packages/dbus/bus.py", line 273, in start_service_by_name
Apr 19 14:13:09 Thinkcentre-M57p cpupower-gui[3417]:     return (True, self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
Apr 19 14:13:09 Thinkcentre-M57p cpupower-gui[3417]:                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 19 14:13:09 Thinkcentre-M57p cpupower-gui[3417]:   File "/usr/lib/python3.11/site-packages/dbus/connection.py", line 634, in call_blocking
Apr 19 14:13:09 Thinkcentre-M57p cpupower-gui[3417]:     reply_message = self.send_message_with_reply_and_block(
Apr 19 14:13:09 Thinkcentre-M57p cpupower-gui[3417]:                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 19 14:13:09 Thinkcentre-M57p cpupower-gui[3417]: dbus.exceptions.DBusException: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.rnd2.cpupower_gui.helper.service not found.
Apr 19 14:13:09 Thinkcentre-M57p systemd[1]: cpupower-gui.service: Main process exited, code=exited, status=1/FAILURE
Apr 19 14:13:09 Thinkcentre-M57p systemd[1]: cpupower-gui.service: Failed with result 'exit-code'.
Apr 19 14:13:09 Thinkcentre-M57p systemd[1]: Failed to start Apply cpupower-gui config at boot.
Thinkcentre-M57p:~>

And

journalctl -xeu cpupower-gui.service
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit cpupower-gui.service has begun execution.
░░ 
░░ The job identifier is 4791.
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]: Traceback (most recent call last):
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:   File "/usr/lib/python3.11/site-packages/dbus/bus.py", line 173, in activate_name_owner
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:     return self.get_name_owner(bus_name)
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:   File "/usr/lib/python3.11/site-packages/dbus/bus.py", line 348, in get_name_owner
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:     return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:   File "/usr/lib/python3.11/site-packages/dbus/connection.py", line 634, in call_blocking
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:     reply_message = self.send_message_with_reply_and_block(
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.rnd2.cpupower_gui.helper': no such name
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]: During handling of the above exception, another exception occurred:
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]: Traceback (most recent call last):
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:   File "/usr/bin/cpupower-gui", line 33, in <module>
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:     from cpupower_gui.helper import (
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:   File "/usr/share/cpupower-gui/cpupower_gui/helper.py", line 16, in <module>
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:     SESSION = BUS.get_object(
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:               ^^^^^^^^^^^^^^^
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:   File "/usr/lib/python3.11/site-packages/dbus/bus.py", line 237, in get_object
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:     return self.ProxyObjectClass(self, bus_name, object_path,
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:   File "/usr/lib/python3.11/site-packages/dbus/proxies.py", line 250, in __init__
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:     self._named_service = conn.activate_name_owner(bus_name)
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:   File "/usr/lib/python3.11/site-packages/dbus/bus.py", line 178, in activate_name_owner
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:     self.start_service_by_name(bus_name)
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:   File "/usr/lib/python3.11/site-packages/dbus/bus.py", line 273, in start_service_by_name
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:     return (True, self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:   File "/usr/lib/python3.11/site-packages/dbus/connection.py", line 634, in call_blocking
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:     reply_message = self.send_message_with_reply_and_block(
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]:                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 19 18:00:04 paul-Thinkcentre-M57p cpupower-gui[15207]: dbus.exceptions.DBusException: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.rnd2.cpupower_gui.helper.service not found.
Apr 19 18:00:04 paul-Thinkcentre-M57p systemd[1]: cpupower-gui.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit cpupower-gui.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 19 18:00:04 paul-Thinkcentre-M57p systemd[1]: cpupower-gui.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit cpupower-gui.service has entered the 'failed' state with result 'exit-code'.
Apr 19 18:00:04 paul-Thinkcentre-M57p systemd[1]: Failed to start Apply cpupower-gui config at boot.
░░ Subject: A start job for unit cpupower-gui.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit cpupower-gui.service has finished with a failure.
░░ 
░░ The job identifier is 4791 and the job result is failed.
lines 130-189/189 (END)

The following lines led me to ask here about the situation:

  1. dbus.exceptions.DBusException: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.rnd2.cpupower_gui.helper.service not found.
  2. Support: systemd-devel Info Page

The application has been working on this machine (with a few glitches) until recently. Can you tell me what you think is going on here?

-Thanks

2

Have you tried asking on forums.opensuse.org?

From the provided logs, this doesn’t seem to be related to KDE.

Did you try logging in into the IceWM session and launch the program from there?

(usually the IceWM session is installed by default on openSUSE installs)

If it also does not launch there, then it is definitely not KDE related.

3

Ok thank you for telling me this. I logged into an IceWM session and could not find cpupower-gui shown in the menu but then in terminal passed: # cpupower-gui -p and the error was also displayed.

1 Like
4

So it is probably a regression on an update unrelated to KDE.

I guess it can be something related to a d-bus or a SystemD update.

5

This looks like a packaging issue from the distro or repo that provided the software.

6

Thank you for your replies. I believe I have found a solution but my exact steps are not exactly documented on this.

I spoke with someone who works with openSUSE packaging and they gave me some more tips to try out.

  1. ls /usr/share/dbus-1/system-services/org.rnd2.cpupower_gui.helper.service
    /usr/share/dbus-1/system-services/org.rnd2.cpupower_gui.helper.service

  2. rpm -ql cpupower-gui
    /usr/share/dbus-1/system-services/org.rnd2.cpupower_gui.helper.service

  3. systemctl list-unit-files --type=service

  4. cpupower-gui-helper.service - had somehow become disabled, so I enabled the service and powercycled the machine.

cpupower-gui service was able to start and it works alright again now.

I was also able to create a cpupower-ondemand-governor.service so the machine starts the kernel using the ondemand governor now.

Things seem to have worked out ok actually. Thank you for your help with this also.

1 Like