| Summary: | Powerdevil ettings not working | ||
|---|---|---|---|
| Product: | [Plasma] Powerdevil | Reporter: | Jan-Peter Rühmann <Jan-Peter> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | major | CC: | bhush94, bizyaev, kde, nate, pieterkristensen |
| Priority: | NOR | ||
| Version: | 5.12.6 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jan-Peter Rühmann
2018-08-20 10:24:09 UTC
What happens if you manually run it from commandline? /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil There is no such Folder, since I am using 32Bit Linux as I´ve stated before. I wil try /usr/lib/i386-linux-gnu/libexec/org_kde_powerdevil instead. Tried it and by running it it solves the problem. How can I make it persistent (running automaticaly at starting KDE)? Thanks, 32-bit compatibility issue maybe? Off-topic for this bug report, but FYI 32-bit support was *almost* dropped from Kubuntu 18.04 due to a lack of testers. The same fate may befall it in 18.10. If you're using the 32-bit version, we would really appreciate it if you could do some beta testing to help keep the 32-bit version alive! Head over to #kubuntu-devel on freenode IRC if you're interested. Used to work for me before, but now in Powerdevil log I get: "Failed to execute program org.kde.powerdevil.backlighthelper: Permission denied". When running `qdbus --system org.kde.powerdevil.backlighthelper`, I get: ``` Error: org.freedesktop.DBus.Error.AccessDenied Rejected send message, 1 matched rules; type="method_call", sender=":1.25" (uid=32011 pid=1944 comm="/usr/lib/qt5/bin/qdbus --system org.kde.powerdevil") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination="org.kde.powerdevil.backlighthelper" (bus) ``` I use Debian Testing. This bug breaks brightness control in Plasma. I had the same strange behavior of powerdevil. Sometimes it doesn't load at startup and sometimes it does but doesn't work. I found the perfect workaround. I made a bash script with the following content: 1) killall /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 2) sleep 10 & 3) /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil </dev/null &>/dev/null & 1) can kill the process when it runs but does nothing, 2) makes execution of 3) wait but doesn't hold the system. And 3) starts powerdevil completely unattached to the terminal. I put the script of course in the folder ~/.config/plasma-workspace/env. That way it runs not only at startup but also after logout. The script never failed me. I know it's no more than a workaround and I'm waiting eagerly for a real solution but for now the problem is solved. I must have been lucky. On an other machine it just won't work, the executable script in /.config/plasma-workspace/env. But then I read here https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/autostart/index.html that there is a bug that makes it impossible for autostart scripts to work from that location. I would really like to find that bug rapport. I looked well again: my machine always loads powerdevil at startup only a lot of times powerdevil does nothing. But also a lot of times it works as it should. I noticed this unpredictable behavior on an other machine too. It also had an Intel cpu from about 2010-2011. On other machines powerdevil always works. Either way, since the problem is powerdevil not running automatically, this seems like it could be a distro configur issue. Can you reproduce the issue in KUbuntu 20.04? I´ve found the Problem ktorrent had interrupt powerdevil. I´ve did not find that directly because it worked flawlessly in the past. |