[Bug 594852] Re: upower gives incorrect data/misleading data

2012-12-07 Thread monochromec
Same thing 12.10. acpi shows 43% full, but according to upower the battery should be almost empty as "upower --dump" reports a percentage of 3.8%. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/594852

[Bug 594852] Re: upower gives incorrect data/misleading data

2012-12-07 Thread Launchpad Bug Tracker
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/594852 Title: upow

[Bug 594852] Re: upower gives incorrect data/misleading data

2011-02-01 Thread Dmitry Gulevich
I am on Alienware M15X, Ubuntu 10.10. UPower does not register that the lid closed after first suspend/resume, while acpi does: > yes "upower --dump | grep lid-is-closed; cat /proc/acpi/button/lid/*/state; sleep 2" | sh lid-is-closed: yes state: closed lid-is-closed: yes state:

[Bug 594852] Re: upower gives incorrect data/misleading data

2010-06-22 Thread David Mack
I've been digging further. It appears my issue may not be with upower. First, my acpi data is consistent with upower --dump. Percentages match, etc. Second, I have found notes from other users (even those using winblows) about battery information being incorrect with my BIOS. Therefore, I believ

[Bug 594852] Re: upower gives incorrect data/misleading data

2010-06-17 Thread am
I didn't notice if mine gives inconsistent reporting of technology, but I can check. Yes, my impression is that upower is a bit buggy. -- upower gives incorrect data/misleading data https://bugs.launchpad.net/bugs/594852 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 594852] Re: upower gives incorrect data/misleading data

2010-06-16 Thread David Mack
Something similar is happening to my computer. Not only is the charge information inconsistent, the reporting technology of the battery also changes inexplicably from Li-ion to Nimh. I believe, in my case, these issues may be related. I have been looking into writing a udev rule to force the correc