https://bugs.kde.org/show_bug.cgi?id=474630
--- Comment #4 from Weihao Jiang <weihau.chi...@gmail.com> --- (In reply to Nate Graham from comment #1) > The slider moving back to the previous setting is an upstream bug; see > https://gitlab.freedesktop.org/hadess/power-profiles-daemon/-/issues/106. > > It also looks like when you have two instances of the widget, their sliders > aren't synced; can you still reproduce that issue with only a single > instance of the widget? I don't think it is the upstream bug you mentioned, because powerprofilectl can successfully handle the change. - By using `Environment="G_MESSAGES_DEBUG=all"` in power-profiles-daemon.service, the debugging log shows that powerprofilectl detects correct profile and internal ACPI changes are not observed. - As shown in the attachment "Screen capture of battery plasmoid display issue", gdbus reports correct ActiveProfile value. - The instance spawned by plasmawindowed (another instance) can handle it successfully. So I assume that it's not a problem from powerprofilectl. Another instance is opened as guided through kde wiki "Plasma/Debugging#Check widgets individually" to check the problem, and the slider issue exists can be reproduced without it. By checking DBus messages with WireShark, I observed difference from the normal one and the moving slider widget. Moving slider one, in status bar ``` 76 8.503382 :1.22 org.kde.Solid.PowerManagement D-Bus 245 setProfile() @ /org/kde/Solid/PowerManagement/Actions/PowerProfile 77 8.510215 :1.61 :1.22 D-Bus 56 -> '' ``` Normal one, started with plasmawindowed ``` 192 20.867629 :1.485 org.kde.Solid.PowerManagement D-Bus 245 setProfile() @ /org/kde/Solid/PowerManagement/Actions/PowerProfile 193 20.905039 :1.61 D-Bus 213 * currentProfileChanged() @ /org/kde/Solid/PowerManagement/Actions/PowerProfile 194 20.905057 :1.61 :1.485 D-Bus 56 -> '' ``` I noticed that the line `currentProfileChanged() @ /org/kde/Solid/PowerManagement/Actions/PowerProfile` is missing from the Moving slider one. Sorry that I'm not familiar with dbus, and I can't understand these values. The dbus I captured are put in the attachments "DBus recorded with Wireshark". -- You are receiving this mail because: You are watching all bug changes.
