This bug existed when ubuntu used devkit-power now it uses upower and its still there so now, as Chris said is it a kernel bug?
This bug existed when ubuntu used devkit-power now it uses upower and its still there so now, as Chris said is it a kernel bug?