https://bugs.kde.org/show_bug.cgi?id=501446
Bug ID: 501446
Summary: Powerdevil cannot request/set brightness on integrated
laptop screen and crashes
Classification: Plasma
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Power management & brightness
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
SUMMARY
It seems a recent update to Powerdevil broke the connection to the Wayland
compositors used to set brightness on displays. I have a Framework Laptop (AMD
7840U processor) and the Powerdevil service fails to connect to the Wayland
compositor to request/set the display's brightness, and I thus lose all access
to brightness control *as well as battery information*, even though the two are
unrelated enough.
STEPS TO REPRODUCE
1. Start a user session in Plasma.
2. See the brightness isn't modifiable. Check `systemctl --user status
plasma-powerdevil.service` and see it has an exit code of 255 (exception).
3. Try to "replace" it using `/usr/libexec/org_kde_powerdevil --replace`
4. Notice the error message is specifically pointing out an error in the
`kde_external_brightness_device` protocol, specifically this message:
```
wl_display#1: error 1: invalid method 5, object
kde_external_brightness_device_v1#39
The Wayland connection experienced a fatal error: Invalid argument
```
OBSERVED RESULT
The brightness is non-controllable, and the battery reporting as well as the
"Power management" KCM are unavailable.
EXPECTED RESULT
The process should fail "gracefully", and still allow for charge reporting to
work when the brightness cannot be controlled for some reason.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.6 GiB of RAM
Graphics Processor: AMD Radeon 780M
ADDITIONAL INFORMATION
It seems to have happened around ~4 weeks ago, maybe the regression happened
with Plasma 6.3? I do not know how I could bisect the commits to find the issue
without having to recompile all Plasma components depending on Powerdevil, I'd
appreciate some guidance.
--
You are receiving this mail because:
You are watching all bug changes.
