No, there is no current_now. Sorry, I should have mentioned that I am using natty currently and thus am in the wrong place to report the bug. Anyway, I get
ls /sys/class/power_supply/BAT0/
alarm energy_full_design power status uevent
cycle_count energy_now power_now subsystem voltage_min_design
device manufacturer present technology voltage_now
energy_full model_name serial_number type
So there is "power_now" and "energy_now", and "power_now" seems to carry the right values. If I take a look at the strings in /usr/lib/upower/upowerd however, it would rather appear that upowerd is instead looking for "charge_now".
So it would seem that we have a discrepancy between the kernel file name, and what upowerd is looking for.
I have no idea what the discrepancy (if any) in Maverick would be.
Looks like I am going to patch the upowerd binary as a first measure.
No, there is no current_now. Sorry, I should have mentioned that I am using natty currently and thus am in the wrong place to report the bug. Anyway, I get
ls /sys/class/ power_supply/ BAT0/
alarm energy_full_design power status uevent
cycle_count energy_now power_now subsystem voltage_min_design
device manufacturer present technology voltage_now
energy_full model_name serial_number type
So there is "power_now" and "energy_now", and "power_now" seems to carry the right values. If I take a look at the strings in /usr/lib/ upower/ upowerd however, it would rather appear that upowerd is instead looking for "charge_now".
So it would seem that we have a discrepancy between the kernel file name, and what upowerd is looking for.
I have no idea what the discrepancy (if any) in Maverick would be.
Looks like I am going to patch the upowerd binary as a first measure.