Your message dated Tue, 31 Jul 2018 15:06:47 +0200
with message-id
<CACiXRdFag25huSz5igbJHc=pf9f2a7+b6jggzs2ls4mme2f...@mail.gmail.com>
and subject line Re: Bug#785398: i3status shows battery percentage as 128.35%
when full
has caused the Debian Bug report #785398,
regarding i3status shows battery percentage as 128.35% when full
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 [email protected]
immediately.)
--
785398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785398
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: i3
Version: 4.10.2-2
Severity: normal
I use last_full_capacity=true with i3status battery module, as quite
obviously current percentage is what most of the users would like to
know, not compared to what they had when the battery was new. This works
fine until the battery is fully charged, when the percentage jumps from
nearly 100% to 128.35% and stays there until I disconnect the charger,
when it drops again slightly under 100% very soon as the battery
discharges.
Could this please be fixed?
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/mksh
Versions of packages i3 depends on:
ii i3-wm 4.10.2-2
Versions of packages i3 recommends:
ii dunst 0.2.0-3
ii i3lock 2.4.1-1
ii i3status 2.5.1-1
ii suckless-tools 38-2
i3 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: i3status
Version: 2.10-1
This was fixed in i3status 2.10
--- End Message ---
