Christophe Schepens, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:
apport-collect -p linux <replace-with-bug-number> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.11-rc3 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: kernel-unable-to-test-upstream kernel-unable-to-test-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: needs-kernel-logs needs-upstream-testing regression- potential ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: needs-full-computer-model -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1133328 Title: Battery design capacity is zero Status in “linux” package in Ubuntu: Incomplete Bug description: Seen on Ubuntu 12.10. I've a Lenovo G780 unit for which the battery design capacity is reported as zero. This is a brand new unit. In /sys/class/power_supply/BAT1 I can find the following information: POWER_SUPPLY_NAME=BAT1 POWER_SUPPLY_STATUS=Charging POWER_SUPPLY_PRESENT=1 POWER_SUPPLY_TECHNOLOGY=Unknown POWER_SUPPLY_CYCLE_COUNT=1491 POWER_SUPPLY_VOLTAGE_MIN_DESIGN=1000 POWER_SUPPLY_VOLTAGE_NOW=11820000 POWER_SUPPLY_POWER_NOW=635500000 POWER_SUPPLY_ENERGY_FULL_DESIGN=0 POWER_SUPPLY_ENERGY_FULL=47520000 POWER_SUPPLY_ENERGY_NOW=36350000 POWER_SUPPLY_MODEL_NAME= POWER_SUPPLY_MANUFACTURER=Li-Ion POWER_SUPPLY_SERIAL_NUMBER=PABAS0241231 At first, I thought that this was a battery issue, but when I use Windows based battery tools, I get good values for the 3 capacity values: design capacity last full charged capacity current capacity These 3 values are different in windows, so it's not that one of the capacity values is reused for one of the other values. This is a Ubuntu defect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1133328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
