SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. own a thinkpad x230 2. unplug the power supply 3. keep an eye on the default system tray's battery icon OBSERVED RESULT the AC connected icon remains on for about 2 minutes, then it updates and plays the chime EXPECTED RESULT the AC disconnected chime should play immediately and update the icon as soon as AC is disconnected SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.25.4 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.9 Qt Version: ADDITIONAL INFORMATION this happens in both kubuntu 21.04 and 21.10 "acpi -V" shows the change immediately, as does "upower -m" which leads me to believe it is a KDE bug
Works as expected with my ThinkPad X1 Yoga.
I guess that's why I'm not running Plasma on wla C64 🙂 > On 16/08/2022, at 5:39 AM, Nate Graham <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=457900 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |nate@kde.org > > --- Comment #1 from Nate Graham <nate@kde.org> --- > Works as expected with my ThinkPad X1 Yoga. > > -- > You are receiving this mail because: > You reported the bug.
do you have any idea which code is responsible for the battery applet? i could possibly workaround by making it read the udev result works fine on windows pe on the same machine over a 4-trial test it took almost exactly 2 minutes each time, with a deviation of +- 5s.
(In reply to arno from comment #3) > do you have any idea which code is responsible for the battery applet? i > could possibly workaround by making it read the udev result > > works fine on windows pe on the same machine > > over a 4-trial test it took almost exactly 2 minutes each time, with a > deviation of +- 5s. also, I am noting this problem does not occur in the previous release and does not occur in GNOME
about 1 in 10 reboots will produce the correct result
Pretty sure this has been fixed