https://bugs.kde.org/show_bug.cgi?id=477805
Kevin Kofler <kevin.kof...@chello.at> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
CC| |kevin.kof...@chello.at
Status|RESOLVED |REOPENED
--- Comment #6 from Kevin Kofler <kevin.kof...@chello.at> ---
Unfortunately, at least the PowerDevil fix (see comment #5) was not backported
to 5.27, and I have just hit this issue on my PinePhone with PowerDevil. The
symptoms:
* I tried to reboot the PinePhone several times; each time, the screen
brightness ruler would do nothing (whereas it used to work just hours before,
without me having upgraded any package in the meantime, though the trigger
might have been the package upgrades from last week).
* So I tried the org.kde.Solid.PowerManagement.Actions.BrightnessControl D-Bus
interface through the qdbus CLI. That worked, magically. Huh?
* So I looked into journalctl -b, and noticed PowerDevil was failing to start
up due to the 5 second timeout, then getting restarted several times, and then
at some point starting to run. So when I checked systemctl status, it was
actually running, but the UI (the Plasma Mobile quicksettings drawer) was not
aware of that, it had failed to connect to PowerDevil on startup and did not
retry (which is arguably a bug in the UI and should probably be reported
separately).
So I copied the unit file to /etc/systemd/user/plasma-powerdevil.service and
increased the timeout to 10 seconds, and everything started working again. Then
I wanted to file a bug, and the duplicate search found this one. I have not yet
tested the upstream fix (the one that went into master), but I expect that to
work, too.
So can we please backport the PowerDevil change to 5.27?
--
You are receiving this mail because:
You are watching all bug changes.
