On Thu, 2007-07-05 at 10:07 +0000, Richard Hughes wrote:
> Guys, have you had better luck with 2.19.x? The battery profiling code
> in 2.19.x should make a lot of these multi-battery issues go away as we
> profile the system state, not the battery.
I have a Thinkpad T20 with two batteries. With Feisty, things seem to
work OK. The battery monitor shows me both the battery levels, and I
have definitely run it down past the first battery.
<thinks>
However, I recall using the fix relating to this value:
/apps/gnome-power-manager/use_time_for_policy
So, the original issue may just be masked for me. However, this
workaround works flawlessly, and I see no reason it couldn't become the
default behavior.
Mark
>
--
. . . . 1997-2007: Ten Years of Excellence. . . . . .
Mark Stosberg Principal Developer
<email address hidden> Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
On Thu, 2007-07-05 at 10:07 +0000, Richard Hughes wrote:
> Guys, have you had better luck with 2.19.x? The battery profiling code
> in 2.19.x should make a lot of these multi-battery issues go away as we
> profile the system state, not the battery.
I have a Thinkpad T20 with two batteries. With Feisty, things seem to
work OK. The battery monitor shows me both the battery levels, and I
have definitely run it down past the first battery.
<thinks>
However, I recall using the fix relating to this value:
/apps/ gnome-power- manager/ use_time_ for_policy
So, the original issue may just be masked for me. However, this
workaround works flawlessly, and I see no reason it couldn't become the
default behavior.
Mark
> www.summersault .com/ . . . . . . . .
--
. . . . 1997-2007: Ten Years of Excellence. . . . . .
Mark Stosberg Principal Developer
<email address hidden> Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://