| Summary: | Powerdevil cannot request/set brightness on integrated laptop screen and crashes | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | thibaulltt <thibaulltt> |
| Component: | Power management & brightness | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | jpetso, nate, xaver.hugl |
| Priority: | NOR | Keywords: | regression |
| Version First Reported In: | 6.3.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/plasma/powerdevil/-/commit/2428305faa3dab46a09193e1998d35b8c644c516 | Version Fixed/Implemented In: | 6.3.5 |
| Sentry Crash Report: | |||
|
Description
thibaulltt
2025-03-13 12:01:57 UTC
Weird question, but could you confirm that the kwin, libkscreen and powerdevil packages were all updated to a 6.3.x version? If I look into the generated file powerdevil/daemon/wayland-kde-external-brightness-v1-client-protocol.h, it defines the constant KDE_EXTERNAL_BRIGHTNESS_DEVICE_V1_SET_OBSERVED_BRIGHTNESS as 5 and I think this might be your "invalid method 5" from the logs. The set_observed_brightness() Wayland request (method) was added in Plasma 6.3, so if one of the involved packages is still on 6.2, I could see things going wrong somewhere. I'm also not an expert on Wayland tooling though, and I don't have the experience to tell under which exact conditions you'd see the pasted error. You're right though that this is where the problem is going to be. Then again, it's Fedora and I wouldn't expect them to hold back one of the packages either. So I'm not quite sure where to start looking. Ah, it seems you've found the problem. Kwin was still at version 6.2.5, because the window decorations I was using (klassy) were not updated to 6.3.x, and thus required the old libkdecorations2 shared lib. Removed klassy, and force-upgraded kwin to the latest version and it all works now. Thanks for the help. While that's fixed, my original bug report still seems valid in the sense that powerdevil should not unconditionally fail when the Wayland connection cannot be established. For example, it handles just fine the fact my battery has no charge thresholds that can be user-settable. But losing battery information because of a conflict of my window manager seems a bit unrelated... (In reply to thibaulltt from comment #2) > While that's fixed, my original bug report still seems valid in the sense > that powerdevil should not unconditionally fail when the Wayland connection > cannot be established. Yeah, that's fair. Thanks for pointing this out, or I would have probably marked the bug as resolved :) A possibly relevant merge request was started @ https://invent.kde.org/plasma/powerdevil/-/merge_requests/539 Git commit fc31698c5be034dcefe8395ed97ab526696671ed by Xaver Hugl, on behalf of Jakob Petsovits. Committed on 14/04/2025 at 13:24. Pushed by zamundaaa into branch 'master'. daemon: Don't crash if using powerdevil 6.3 with kwin 6.2 M +6 -2 daemon/controllers/externalbrightnesscontrol.cpp https://invent.kde.org/plasma/powerdevil/-/commit/fc31698c5be034dcefe8395ed97ab526696671ed Git commit 2428305faa3dab46a09193e1998d35b8c644c516 by Xaver Hugl. Committed on 14/04/2025 at 13:31. Pushed by zamundaaa into branch 'Plasma/6.3'. daemon: Don't crash if using powerdevil 6.3 with kwin 6.2 (cherry picked from commit fc31698c5be034dcefe8395ed97ab526696671ed) Co-authored-by: Jakob Petsovits <jpetso@petsovits.com> M +6 -2 daemon/controllers/externalbrightnesscontrol.cpp https://invent.kde.org/plasma/powerdevil/-/commit/2428305faa3dab46a09193e1998d35b8c644c516 |