I have the same finding as Sergey, and I'm tried both the nvidia driver
from nvidia-311, and nvidia-311-updates
$ upower --dump
Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path: BAT0
vendor: Panasonic
model:42T4801
serial:
Another note:
The issue appears when I activate nvidia driver - nvidia-331.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1240673
Title:
Reports 0% charged for fully charged batteries
Note for my last comment:
The system detects battery without any problems and battery indicator
works fine in KDE when I boot from Kubuntu 14.04 installation DVD. The
battery indicator works fine after I install Kubuntu 14.04 to hard disk,
but stop work after I did 'dist-upgrade' on installed sys
Hi!
I have same problem on my Dell Inspiron 7737 notebook with Ubuntu 14.04.
the output of upower --dump is:
-
corwin@corwin-Inspiron-7737:~$ LANG=C upower --dump
Device: /o
This bug was fixed in the package upower - 0.9.22-1ubuntu2
---
upower (0.9.22-1ubuntu2) saucy-proposed; urgency=low
* Add 00git_clamp_percentage.patch: Clamp percentage for overfull batteries,
to avoid showing 0% on some fully charged battery models. Fixes regression
from 0.
I installed
http://ru.archive.ubuntu.com/ubuntu/pool/main/u/upower/upower_0.9.23-2_amd64.deb
and in a few seconds my battery went from empty to fully charged. The
shortest charging time ever ;-)
Dell Latitude E6530
--
You received this bug notification because you are a member of Desktop
Package
Fixed on Dell Latitude E6520
Thank you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1240673
Title:
Reports 0% charged for fully charged batteries
Status in “upower” package in Ubun
** Branch linked: lp:debian/upower
** Branch linked: lp:ubuntu/upower
** Branch linked: lp:ubuntu/saucy-proposed/upower
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1240673
Title:
Fixed on Dell N5010.
Thank you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1240673
Title:
Reports 0% charged for fully charged batteries
Status in “upower” package in Ubuntu:
F
Ok, I installed the new upower package, and it works on my Dell Latitude
E5530, now the battery applet shows 100% on full charge.
Here is the output of:
upower --dump
Device: /org/freedesktop/UPower/devices/line_power_AC
native-path: AC
power supply: yes
updated:
costavi [2013-10-23 15:20 -]:
> is the fixed pachage already available in the 'proposed' repository?
Yes, it is:
upower | 0.9.22-1ubuntu1 | saucy | source, amd64, arm64, armhf,
i386, powerpc
upower | 0.9.22-1ubuntu2 | saucy-proposed | source, amd64, arm64, armhf,
i386, power
I would like to test the new package, but
is the fixed pachage already available in the 'proposed' repository?
Because, once added the 'proposed' repository I receive the following
update proposals:
glib-networking glib-networking-common glib-networking-services kubuntu-docs
libglib2.0-0
libgl
Installed the updated package and it now works as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1240673
This bug was fixed in the package upower - 0.9.23-2
---
upower (0.9.23-2) unstable; urgency=low
* Drop hardcoded binary glib dependency, it's already being generated
automatically from the versioned build depends.
* Add 00git_clamp_percentage.patch: Clamp percentage for overf
Hello Scott, or anyone else affected,
Accepted into saucy-proposed. The package will build now and be
available in a few hours in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -prop
Saucy SRU uploaded.
** Description changed:
+ SRU INFORMATION:
+ Explanation: This bug was introduced with
http://cgit.freedesktop.org/upower/commit/?id=07b95b8e which preferred the
kernel's reported percentage ("capacity" sysfs attribute") over calculating it
from energy/charge. This exposed
I backported the patch and uploaded it to Debian. Will sync it as soon
as it gets imported.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1240673
Title:
Reports 0% charged for fully c
** Also affects: upower (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: upower (Ubuntu Trusty)
Importance: High
Assignee: Martin Pitt (pitti)
Status: Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which
On Tuesday, October 22, 2013 08:07:54 you wrote:
> Fixed upstream with a test case:
> http://cgit.freedesktop.org/upower/commit/?id=22da1a0bc Also cherry-picked
> into 0.9 branch.
I rebuilt the package locally with the patch and that (not surprisingly)
solved the problem. I think this should, in
Fixed upstream with a test case:
http://cgit.freedesktop.org/upower/commit/?id=22da1a0bc
Also cherry-picked into 0.9 branch.
** Changed in: upower (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is su
Reproduced in test suite:
TI:09:55:58 energy 132,00 bigger than full 120,00
(lt-upowerd:8664): GLib-GObject-WARNING **: value "110,00" of type
'gdouble' is invalid or out of range for property 'percentage' of type
'gdouble'
That's how it ends up as 0%.
** Changed in: upower (Ubu
These are indeed odd, I guess that's what is upsetting upower:
/sys/class/power_supply/BAT0/charge_now:600
/sys/class/power_supply/BAT0/charge_full:4615000
/sys/class/power_supply/BAT0/capacity:130
/sys/class/power_supply/BAT2/charge_now:280
/sys/class/power_supply/BAT2/charge_full:227600
Attached grep -r . /sys/class/power_supply/* from a Dell Latitude E6320
** Attachment added: "grep -r . /sys/class/power_supply/* on Dell Latitude
E6320"
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1240673/+attachment/3886622/+files/upower_grep
--
You received this bug notificatio
Sounds like fallout from
http://cgit.freedesktop.org/upower/commit/?id=07b95b8e or some similar
changes. So this is an inverse kernel/hardware bug to the problem of
phone batteries from that commit. *sigh* So we need to add some more
heuristics for this case, too.
I have a pretty good idea what ha
Same problem:
Manufacturer: Dell Inc.
Product Name: Latitude E6520
Version: 01
upower -i /org/freedesktop/UPower/devices/battery_BAT0
native-path: BAT0
vendor: SMP
model:DELL 5G67C21
serial: 278
power supply:
Dell Latitude E6430 affected too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1240673
Title:
Reports 0% charged for fully charged batteries
Status in “upower” package in Ubuntu:
I have the same problem with mye Dell Latitude E5530, as reported on this
(duplicate) bug report:
https://bugs.launchpad.net/ubuntu/+source/kde-baseapps/+bug/1235633
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https
Same problems on a Dell Latitude E6520 with a 100Wh battery
vendor: Samsung SDI
model:DELL V57XN23
It seems that although state is "fully-charged" the percentage is 0% instead of
100%.
This is what the KDE applet reports most probably so it seems to be a upower
Now it's back to 0% on both batteries after just a suspend/resume (it
was plugged into power when suspended and when resumed, although it had
been unplugged while suspended):
$ upower --dump
Device: /org/freedesktop/UPower/devices/line_power_AC
native-path: AC
power supply: ye
Confirmed on Dell N5010
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1240673
Title:
Reports 0% charged for fully charged batteries
Status in “upower” package in Ubuntu:
Confirmed
** Tags added: kubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1240673
Title:
Reports 0% charged for fully charged batteries
Status in “upower” package in Ubuntu:
Confirmed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upower (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/124067
After unplugging it and plugging it back in, it's now reporting correct
information for one battery:
$ upower --dump
Device: /org/freedesktop/UPower/devices/line_power_AC
native-path: AC
power supply: yes
updated: Thu 17 Oct 2013 09:51:58 AM EDT (496 seconds ago
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1240673
** Tags added: iso-testing
--
You received this bug notification because you are a member of Desktop
Packages, which
34 matches
Mail list logo
