Summary: | Scrolling to Change Power Profile on Power Management Icon Takes a Lot of Scrolling | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Eamonn Rea <eamonnrea> |
Component: | Power and Battery widget | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kde, me, natalie_clarius, nate |
Priority: | NOR | ||
Version: | 6.1.0 | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Eamonn Rea
2024-06-21 22:47:59 UTC
This is very likely an issue with something upstream, wither power-profiles-daemon, or your vendor-supplied system firmware: sometimes when you change the profile, it immediately changes back, and the UI is simply reflecting this bug. Very annoying for sure. But how do you know? Try setting the profile with `powerprofilesctl set performance` and then run `powerprofilesctl` to see if the profile has been changed to performance mode. If it's still on balanced or power saver, it's an upstream bug. See for example: https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/issues/106 That's been closed and locked though, traced to a firmware problem with the vendor-supplied firmware. If you find that it's an upstream bug, feel free to open a new one there, as yours may be something else. > sometimes when you change the profile, it immediately changes back, and the UI is simply reflecting this bug. Very annoying for sure.
Even if the text on the tooltip itself never changes, but does change and stays correct if I keep scrolling?
Ok, I mis-diagnosed this, sorry. I can't reproduce the issue of touchpad scrolling to change the value being excessively... scrolly. Have you changed the default scroll speed at all? Does it reproduce in a new clean user account on the same machine? I have changed the scroll speed, yes.I have it at the lowest setting (which is still a bit fast for my tastes). I have not tried a new user account, but this one is pretty fresh (just over a week old). If I do a "fling" gesture (not sure how to word it, sorry) where I swipe vertically with two fingers really fast it will pretty consistently actually change. But gradually scrolling like I would do for, say, volume, requires quite a lot of scrolling (usually two full scrolls). Aha! Now I'm 99% sure this is Bug 470746. Can you reset the scroll speed to normal and see if it goes away? If so, it's Bug 470746. Yup, good catch! Turning the scroll speed back to default (as per Bug 470746, the 5th tick from the left on the slider) and the scroll events trigger properly. It is worth noting that from what I have observed, all other scroll behaviour is fine, including those on other widgets such as the Volume widget. Scrolling on that changes the volume as expected, this seems to only impact Power Management. That doesn't mean it *isn't* Bug 470746 but it is an inconsistency in that this only appears to affect Power Management, at least in my case. The power profile item has only three items and `snapMode: PlasmaComponents3.Slider.SnapAlways` set on it, which makes its behavior more "discrete" compared to other sliders that can be moved continuously. Do you have keyboard brightness exposed in the widget? If so, try scrolling there too; I'm guessing it has the same problem. Regardless, yeah, this is Bug 470746. *** This bug has been marked as a duplicate of bug 470746 *** > Do you have keyboard brightness exposed in the widget? If so, try scrolling there too; I'm guessing it has the same problem.
I can not, keyboard brightness is not exposed for any of my keyboards or devices (none of my laptops or external keyboards have their brightness show up in any software), it can only be controlled on the keyboards themselves.
But I appreciate the insight, I'm guessing other sliders either have a different snapMode or no snapMode. Took a look around plasma-desktop out of interest and didn't see a snapMode defined for what looked like volume-related slider QML :-) Interesting either way.
And yup, a duplicate of the bug mentioned.
|