| View previous topic :: View next topic |
| Author |
Message |
leyvi
Tux's lil' helper
Joined: 08 Sep 2023
Posts: 99
|
 Posted: Sun Jan 05, 2025 1:14 am Post subject: KDE power management tab in system settings doesn't work |
 |
|
Hello all, when I try to open system settings and go to the "power management" page, it says: "Power Management settings could not be loaded.".
Not sure why, found this thread, and also several others.
Confirmed that `upower`, `dbus`, etc. were all running.
Wondering if the thread mentioned above is relevant to Gentoo, and if so, need it be classified as a bug?
Maybe we need slotting for `ddcutils` or something... |
|
| Back to top |
|
 |
rab0171610
Guru
Joined: 24 Dec 2022
Posts: 450
|
| Posted: Sun Jan 05, 2025 8:36 am Post subject: |
|
|
How do you think that thread is related to your problem? The problem that was specific to that thread was fixed in a previous version of ddcutil. That version in Arch (2.1.0-2.) is lower than the current version in Gentoo (2.1.4) Also, that thread is almost a year old. The only commonality is that a tab in KDE system settings would not load correctly.
You are free to test the 6 versions available in Gentoo if you think that is related to your problem, however only 2 are stabilized.
Whether or not you file a bug is up to you since you are the one having the problem but your problem is not likely anything to do with ddcutil.
Is powerdevil running?
| Code: | | ps -ef | grep power |
which should return something like:
| Code: |
user /usr/libexec/power-profiles-daemon
user /usr/libexec/org_kde_powerdevil
root /usr/libexec/upowerd |
If you do not see it, you can try starting it (as your user not as root):
| Code: | | /usr/libexec/org_kde_powerdevil |
and then try launching system settings again.
To get more helpful output, you can quickly launch the power profiles kcm from the command line:
| Code: | | kcmshell6 kcm_powerdevilprofilesconfig |
It may give better information as to why the module is not loading. |
|
| Back to top |
|
|
leyvi
Tux's lil' helper
Joined: 08 Sep 2023
Posts: 99
|
| Posted: Sun Jan 05, 2025 10:31 am Post subject: |
|
|
Hey dude, I appreciate the help, I'll give it a shot.
On a seperate note:
| Quote: |
PostPosted: Sun Jan 05, 2025 8:36 am Post subject:
How do you think that thread is related to your problem? The problem that was specific to that thread was fixed in a previous version of ddcutil. That version in Arch (2.1.0-2.) is lower than the current version in Gentoo (2.1.4) Also, that thread is almost a year old. The only commonality is that a tab in KDE system settings would not load correctly.
You are free to test the 6 versions available in Gentoo if you think that is related to your problem, however only 2 are stabilized.
Whether or not you file a bug is up to you since you are the one having the problem but your problem is not likely anything to do with ddcutil. |
In the future you may want to be a bit more polite in your replies. Whether or not you intended it, you sound extremely frustrated and impatient in your reply. These forums operate on a purely volunteer basis, from my understanding. If you find helping others directly so infuriating, perhaps you should consider helping others in a different way.
I read the manuals. I read the wiki pages. I did some searching for solutions online, and when nothing I found while searching worked, then I came here. I did everything by the book (tell me if I'm wrong), and I see no reason to be frustrated with the existence of this thread.
Hope this wasn't uncalled for. |
|
| Back to top |
|
|
leyvi
Tux's lil' helper
Joined: 08 Sep 2023
Posts: 99
|
| Posted: Sun Jan 05, 2025 2:21 pm Post subject: |
|
|
Tried it, and you were right: /usr/libexec/org_kde_powerdevil was not running.
Running it fixed the problem.
I'm going to see if there's a config file in /etc that needs my attention. |
|
| Back to top |
|
|
leyvi
Tux's lil' helper
Joined: 08 Sep 2023
Posts: 99
|
| Posted: Sun Jan 05, 2025 2:34 pm Post subject: |
|
|
OK, I've found the issue, it's with the config, and it's not my doing.
This is /etc/xdg/autostart/powerdevil.desktop.
You can see the following line in the file: | Code: | | Exec=/usr/lib64/libexec/org_kde_powerdevil |
This file doesn't actually exist; hence trying to autostart it fails.
The file /usr/libexec/org_kde_powerdevil does exist however, and that's what should be there.
I'll bet someone made a mistake with the relevant ebuild, whichever one that is. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22938
|
| Posted: Sun Jan 05, 2025 3:25 pm Post subject: |
|
|
| leyvi wrote: | On a seperate note: | Quote: | | PostPosted: Sun Jan 05, 2025 8:36 am Post subject: |
|
You can, and generally should, use the forum's quote attribution instead of pasting the control information here. If the attribution is ambiguous, you can additionally use the [post] tag to point your quote to a specific source post. For demonstration purposes, my quote of you above does that: observe how it not only shows your name, but links to the post in which you wrote the text I am quoting. Unfortunately, the forum's native quote only puts your name, but not a back link to the post. The back link must be added manually. | leyvi wrote: | | In the future you may want to be a bit more polite in your replies. Whether or not you intended it, you sound extremely frustrated and impatient in your reply. These forums operate on a purely volunteer basis, from my understanding. If you find helping others directly so infuriating, perhaps you should consider helping others in a different way. |
I cannot speak to rab0171610's state of mind when that was written, but I do not see frustration in the post you quoted. I have previously written similar posts, where the querent expressed conclusions that I felt were not supported by, and possibly even were contradicted by, the evidence cited. In such cases, I ask for an explanation of why the querent believes the evidence presented supports the conclusion stated, with the hope that the querent will either present better evidence, or explain how the existing evidence supports the conclusion, or that the research attempting to craft such an answer will lead the querent to realize that the conclusion was incorrect. In the last case, it may teach the querent more about the system in question, allowing them to reach better conclusions in the future.
In this case, rab0171610 even went to the trouble of enumerating some of the ways that you might have thought them related, and describing why rab0171610 believed those did not support your belief. | leyvi wrote: | | I read the manuals. I read the wiki pages. I did some searching for solutions online, and when nothing I found while searching worked, then I came here. I did everything by the book (tell me if I'm wrong), and I see no reason to be frustrated with the existence of this thread. |
rab0171610 did not post complaining that you need to read more documentation, so I think it is premature to assume that you had received an RTFM response. | leyvi wrote: | OK, I've found the issue, it's with the config, and it's not my doing.
This is /etc/xdg/autostart/powerdevil.desktop.
You can see the following line in the file: | Code: | | Exec=/usr/lib64/libexec/org_kde_powerdevil |
This file doesn't actually exist; hence trying to autostart it fails.
The file /usr/libexec/org_kde_powerdevil does exist however, and that's what should be there.
I'll bet someone made a mistake with the relevant ebuild, whichever one that is. |
What ebuild owns the incorrect file? How does the ebuild generate that file? Have you checked that a fresh install of the ebuild is still wrong? Since the file is in /etc, it's possible that the path you saw was once right, and that a missed or incorrect conflict resolution allowed it to persist even after the ebuild switched to the new and correct path. |
|
| Back to top |
|
|
leyvi
Tux's lil' helper
Joined: 08 Sep 2023
Posts: 99
|
| Posted: Sun Jan 05, 2025 4:32 pm Post subject: |
|
|
OK, I did some digging:
If you look in the source tarball for kde-plasma/powerdevil, you'll find this file (daemon/powerdevil.desktop.cmake), containing the following line: | Code: | | Exec=@KDE_INSTALL_FULL_LIBEXECDIR@/org_kde_powerdevil |
I can't find where `KDE_INSTALL_FULL_LIBEXECDIR` is defined, though. Nothing interesting shows up when I navigate to the root directory of the tarball and run: | Code: | | grep -r "KDE_INSTALL_FULL_LIBEXECDIR" |
Only where the variable is used shows up, and I didn't see anything in the ebuild file either. Does anyone know where `KDE_INSTALL_FULL_LIBEXECDIR` is defined? |
|
| Back to top |
|
|
rab0171610
Guru
Joined: 24 Dec 2022
Posts: 450
|
| Posted: Sun Jan 05, 2025 5:18 pm Post subject: |
|
|
https://bugs.gentoo.org/928345
There is some history with regards to that variable. That link may or may not offer some insight.
If that is what is causing the issue, I would consider filing a bug, especially now that you have more
information.
Also:
https://bugs.gentoo.org/943653 |
|
| Back to top |
|
|
leyvi
Tux's lil' helper
Joined: 08 Sep 2023
Posts: 99
|
| Posted: Sun Jan 05, 2025 7:26 pm Post subject: |
|
|
| From the looks of it, they already fixed the bug; it was in `ecm.eclass`. So what's going on with my system? |
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 9321
|
|
| Back to top |
|
|
leyvi
Tux's lil' helper
Joined: 08 Sep 2023
Posts: 99
|
| Posted: Sun Jan 05, 2025 8:20 pm Post subject: |
|
|
 No, I wasn't aware of that. Guess I'll just run `dispatch-conf`... |
|
| Back to top |
|
|
leyvi
Tux's lil' helper
Joined: 08 Sep 2023
Posts: 99
|
| Posted: Sun Jan 05, 2025 8:56 pm Post subject: |
|
|
| Thanks for all the patience! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
