Summary: | Kubuntu 22.04, Battery widget shows laptop as connected to power source while running on battery | ||
---|---|---|---|
Product: | [Plasma] Powerdevil | Reporter: | Michael Braxner <braxner.michael> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | braxner.michael, nate |
Priority: | NOR | ||
Version: | 5.24.4 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Michael Braxner
2022-04-28 13:00:15 UTC
... and forgot to attach the logs again ... duh After boot on battery ONLY the widget works as it should. Logs BEFORE plugging in power supply: 4/28/22 9:32 AM dbus-daemon [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.28' (uid=0 pid=671 comm="/usr/sbin/thermald --systemd --dbus-enable --adapt" label="unconfined") 4/28/22 9:32 AM systemd Starting Daemon for power management... 4/28/22 9:32 AM dbus-daemon [system] Successfully activated service 'org.freedesktop.UPower' 4/28/22 9:32 AM systemd Started Daemon for power management. 4/28/22 9:32 AM upower.service treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001 4/28/22 9:32 AM upower.service treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:002 4/28/22 9:32 AM powertop Leaving PowerTOP 4/28/22 9:32 AM upower.service treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:003 4/28/22 9:32 AM systemd Finished PowerTOP auto tune. 4/28/22 9:33 AM dbus-daemon [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.59' (uid=1000 pid=1396 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") (using servicehelper) 4/28/22 9:33 AM dbus-daemon [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper' 4/28/22 9:33 AM dbus-daemon [system] Activating service name='org.kde.powerdevil.chargethresholdhelper' requested by ':1.59' (uid=1000 pid=1396 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") (using servicehelper) 4/28/22 9:33 AM dbus-daemon [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper' 4/28/22 9:33 AM dbus-daemon [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.59' (uid=1000 pid=1396 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") (using servicehelper) 4/28/22 9:33 AM dbus-daemon [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' 4/28/22 9:33 AM dbus-daemon [session uid=1000 pid=1073] Activating via systemd: service name='org.kde.KScreen' unit='plasma-kscreen.service' requested by ':1.27' (uid=1000 pid=1396 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") After plugging in power supply: 4/28/22 9:41 AM dbus-daemon [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.59' (uid=1000 pid=1396 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") (using servicehelper) 4/28/22 9:41 AM dbus-daemon [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Battery widget reports charging accurately. Now, after disconnecting the power supply, returning to battery only, NO further log messages occur, i.e. the system apparently did not recognize that the power supply was disconnected ... is this an ACPI problem? Just to clarify: After a COLD boot WITH the power adapter plugged in, the described behaviour does NOT occur. A subsequent restart, suspend or hibernate, either with power supply plugged in or battery alone, does NOT lead to the behaviour described. After a COLD boot ON BATTERY ALONE, the behaviour occurs invariably, and is subsequently NOT remedied by a RESTART WITH power adapter plugged in. It's a bug in the kernel itself. See the discussion and links in Bug 423556. *** This bug has been marked as a duplicate of bug 423556 *** |