Description of problem: cpupower fails to start on fully updated mga9. Just a quick flash of HDD activity and then nothing. menu link or console neither works. Version-Release number of selected component (if applicable):cpupower-gui-1.0.0-1.20220118.1.mga9.rpm How reproducible: click on it in the start menu or run from console Steps to Reproduce: 1.Try to start cpupower-gui. menu entry or console 2. 3.
Created attachment 13760 [details] console output same output as user or root
Confirming the issue. Assigning to our registered cpupower-gui maintainer.
Assignee: bugsquad => rverscheldeCC: (none) => marja11
Just got an update: cpupower-gui-1.0.0-1.20230122.1.mga9 Same problem
Created attachment 13761 [details] console output after package update
CC David who started working on the update. I couldn't reproduce the issue myself with version 1.20220118.1.mga9, but now with the new 1.20230122.1.mga9 I do have the same error. It works after running `systemctl start cpupower-gui-helper.service` manually.
CC: (none) => geiger.david68210
Summary: cpupower-gui fails to start => cpupower-gui fails to start: Could not get owner of name 'org.rnd2.cpupower_gui.helper'
Good job! It's working now after running `systemctl start cpupower-gui-helper.service` Thank you everyone
Marking this as resolved. Thanks everyone.
Solved. Thank you everyone.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
From package description: "System and user systemd units are provided for the user to enable manually, as needed."
I believe that part of the description refers to: ``` ## systemd units Since version 0.9.0, two systemd units have been added; a "system" and a "user" one. The `cpupower-gui.service` applies the configuration as defined in `/etc/cpupower_gui.conf` during boot. The `cpupower-gui-user.service` applies the user configuration during login (see notes below). ``` But `cpupower-gui-helper.service` seems required for the software to be usable, so it should be auto-enabled when installed. The `%post` section is supposed to do that but it doesn't seem to work.
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
*** Bug 33340 has been marked as a duplicate of this bug. ***
CC: (none) => joselp
This issue should be fixed in next cpupower-gui-1.0.0-1.20230122.1.1.mga9.noarch.rpm update removing our mageia systemd post/preun command, which does not seem to work, with "systemctl enable/disable cpupower-gui-helper" general systemd command. Assigning to QA, Package in 9/Core/Updates_testing: ===================== cpupower-gui-1.0.0-1.20230122.1.1.mga9.noarch.rpm From SRPMS: cpupower-gui-1.0.0-1.20230122.1.1.mga9.src.rpm
Source RPM: cpupower-gui-1.0.0-1.20220118.1.mga9.src.rpm => cpupower-gui-1.0.0-1.20230122.1.mga9.src.rpmAssignee: rverschelde => qa-bugsVersion: Cauldron => 9
Keywords: (none) => advisory
Install current version LC_ALL=C urpmi cpupower-gui https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/cpupower-gui-1.0.0-1.20230122.1.mga9.noarch.rpm installing cpupower-gui-1.0.0-1.20230122.1.mga9.noarch.rpm from /var/cache/urpmi/rpms Preparing... ################################################################################################## 1/1: cpupower-gui ################################################################################################## confirm the fail LC_ALL=C urpmi --auto --auto-update medium "QA Testing (32-bit)" is up-to-date medium "QA Testing (64-bit)" is up-to-date medium "Core Release (distrib1)" is up-to-date medium "Core Updates (distrib3)" is up-to-date medium "Nonfree Release (distrib11)" is up-to-date medium "Nonfree Updates (distrib13)" is up-to-date medium "Tainted Release (distrib21)" is up-to-date medium "Tainted Updates (distrib23)" is up-to-date medium "Core 32bit Release (distrib31)" is up-to-date medium "Core 32bit Updates (distrib32)" is up-to-date medium "Nonfree 32bit Release (distrib36)" is up-to-date medium "Tainted 32bit Release (distrib41)" is up-to-date medium "Tainted 32bit Updates (distrib42)" is up-to-date installing cpupower-gui-1.0.0-1.20230122.1.1.mga9.noarch.rpm from //home/katnatek/qa-testing/x86_64 Preparing... ################################################################################################## 1/1: cpupower-gui ################################################################################################## Created symlink /etc/systemd/system/dbus-org.rnd2.cpupower_gui.helper.service -> /usr/lib/systemd/system/cpupower-gui-helper.service. 1/1: removing cpupower-gui-1.0.0-1.20230122.1.mga9.noarch ################################################################################################## The application start as normal user without issues
Whiteboard: (none) => MGA9-64-OKCC: (none) => andrewsfarm
And uninstall without issues LC_ALL=C urpme cpupower-gui removing cpupower-gui-1.0.0-1.20230122.1.1.mga9.noarch Removed "/etc/systemd/system/dbus-org.rnd2.cpupower_gui.helper.service". removing package cpupower-gui-1.0.0-1.20230122.1.1.mga9.noarch 1/1: removing cpupower-gui-1.0.0-1.20230122.1.1.mga9.noarch ################################################################################################## writing /var/lib/rpm/installed-through-deps.list
Validating.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
mga9-64, my workstation "svarten": OK basically. cpupower-gui launches nicely and I can shut down and restart cores. --- Weird things, out of scope of this bug: § The window is invisible in the Plasma panel desktop switcher. § If I switch off a core and enable it again, the min and max fields are still showing zero for that core and governor field say Offline! While it displays the current speed dynamically. § Max freq is 2,9 GHz, but it displays cores running at 3,6 GHz cpupower (non gui) display the same. Even with BIOS set to over drive, if it say max is 2,9 why do run at 3,5 ?
CC: (none) => fri
> § The window is invisible in the Plasma panel desktop switcher. ...and is also not listed in the activity manager.
Installing the latest version from the test repositories, the application now opens correctly.
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0151.html
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED