Bug 426985 - Missdetected AC chord status on lenovo T480
Summary: Missdetected AC chord status on lenovo T480
Status: RESOLVED UPSTREAM
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.19.90
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL: https://gitlab.freedesktop.org/upower...
Keywords:
: 449967 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-09-26 10:24 UTC by Romain D.
Modified: 2022-02-10 20:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Romain D. 2020-09-26 10:24:27 UTC
SUMMARY

Plasmashell returns invalid AC-chord connection status: even when the AC chord is unplugged, plasmashell considers it connected, which causes problematic side-effects like preventing the laptop to suspend when the lid is closed (considering it's still on AC).

STEPS TO REPRODUCE
1. AC-chord connected: indication of battery charging
> acpi
Battery 0: Charging, 77%, 00:17:52 until charged

2. AC-chord disconnected: indication of "plugged but still discharging"
> acpi
Battery 0: Discharging, 77%, discharging at zero rate - will never fully discharge.

OBSERVED RESULT

above

EXPECTED RESULT

AC to show disconnected when effectively so

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.8.11-200.fc32.x86_64 (Fedora)
(available in About System)
KDE Plasma Version: 5.19.90 (but similar issues on 5.18.5)
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
feel free to ask :)
Comment 1 Romain D. 2020-09-26 14:50:35 UTC
the "will never fully discharge" indication by acpi is a bit bugous, though, but after some seconds it normalizes:

> acpi
Battery 0: Discharging, 99%, 04:01:22 remaining

but even in this case, plasma is still reporting that the battery is plugged in.
Comment 2 Nate Graham 2020-09-26 15:22:49 UTC
I have the same issue on my ThinkPad X1 Yoga. Unfortunately it is an upstream upower bug that we can't feasibly work around: https://gitlab.freedesktop.org/upower/upower/-/issues/126
Comment 3 Romain D. 2020-09-26 15:35:22 UTC
Hi Nate, thanks for bringing that up :)
Comment 4 Nicolas Fella 2022-02-10 20:11:09 UTC
*** Bug 449967 has been marked as a duplicate of this bug. ***