[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#785413: marked as done (Wrong battery status when charging on Acer C720P)

Your message dated Sat, 08 May 2021 11:55:36 -0700 (PDT)
with message-id <6096dea8.1c69fb81.99278.8044@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #785413,
regarding Wrong battery status when charging on Acer C720P
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
785413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785413
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux
Version: 3.16.0-4

Hello,

I am running Debian testing on an Acer C720P (amd64), and I am seeing a
strange behavior.  When I charge my battery, it is never reported as
completely charged by the system.  The notebook's led keeps indicating
that the battery is being charged, and when I look at
mate-power-control's battery icon it also says that the battery is not
fully charged.

If I check the values on
/sys/bus/acpi/drivers/battery/PNP0CA\:00/power_supply/BAT0/*, I see
that:

1) It indicates that the battery's charge_now is equal to the battery's
charge_full.

2) It still indicates a "Charging" status.

I still have not investigated it further, so I am opening this bug
against the Linux package (it seems like an ACPI problem).

It is worth mentioning that I was running Fedora before I put Debian on
this machine, and the battery was charging normally there.  Also, I
recently compiled the latest version of the Linux-libre kernel (4.0.3),
and I was seeing the same problem using it as well.  This may mean that
(a) this notebook needs some kind of proprietary blob in this case, or
(b) some userspace program is the actual responsible for this (although
we should also consider the wrong "Charging" status on /sys, as
mentioned above).

You will probably need more specific information to debug this, so
please let me know what I must provide.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: