On Thu, 2010-09-23 at 23:38 +0100, Mark Shuttleworth wrote: > OK. Those are good detailed reports. Is there a bug open for each of > them? We're going to nail g-p-m issues in 11.10, we know that's a bit of > a swamp and have a plan to ask a contractor to help drain it in the next > round. If you're interested, let me know, otherwise good bug reports > would be most useful and will get addressed. > > Mark >
Yes, like I said I reported them all: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/144830 This bug is mostly fixed in 10.04, but only problem remaining is that g-p-m doesn't update its properies window when I plug batter after login. Granted its not possible currently to tell if system has battery before its plugged, but after it is g-p-m should update the properties window. I discussed that on LKML, and more or less nothing came out of that. We ended up with the decision that kernel need to present somehow a flag to userspace that battery bay exists, but no battery present. https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/496221 This bug deals with too low hibernate thresholds. Its piece of cake to fix. All its needed is to make system hibernate as soon as battery hits 5% (or to be safe 10%). (And let user override that to lower value if user really fells like he wants to). Besides, it happened to me that due to natural LiION decay, battery might die on as high as 10% percent. (but on next boot, the total amount of energy it can store is reduced, so it doesn't happen again. https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/616443 10.10 bug, maybe in my case a bit different. I just see the battery status twice, in exact same way. I am sure that some code adds it twice to indicator-applet. https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/645370 This deals with forced screensaver on suspend. To be honest, I didn't report that bug for long time, and today while searching though g-p-m bugs I found this new report. As a side note I also seen many more g-p-m issues, but they mostly are kernel related unlike mine. Also just a small note about the fact that due to variate of ways brightness can be set from hardware keys, g-p-m often doesn't let keyboard set the bightness (usually because it is set i hardware or kernel acpi 'video' driver. As a result of this users with remote controls that have brightness up/down keys can't use them. I think these are all the bugs. Best regards, Maxim Levitsky -- Battery status line too long https://bugs.launchpad.net/bugs/619816 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
