[gutsy] power manager powersave mode works incorrectly

It only appears to happen when the system is initially started on AC...booting the laptop on battery doesn't exhibit the problem.

but will if plugged in and then unplugged

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

To reproduce, choose powersave as the cpu frequency scaling policy when on battery, plug in the laptop if booted from battery, unplug the laptop, and wait ~20 seconds. Check the cpu frequency by mousing over the Power Manager icon.

Choosing an alternative policy (dynamic, for example) and then changing back appears to correct it until the laptop is plugged in, and then unplugged again.

Joshua, I still cannot reproduce this problem on HP nw8240 with up-to-date gutsy.

Can you attach screenshot of your powermanager settings?
Do you get notification when you plug/unplug power that says "CPU frequency policy changed to Xxxx"?

Unfortunately that laptop is no longer functional. They were the
default settings, and I did get the message that it was changing
policy. It just then ramped the cpu frequency to the hilt.

On 10/9/07, Luka Renko <email address hidden> wrote:
> Joshua, I still cannot reproduce this problem on HP nw8240 with up-to-
> date gutsy.
>
> Can you attach screenshot of your powermanager settings?
> Do you get notification when you plug/unplug power that says "CPU frequency
> policy changed to Xxxx"?
>
> ** Changed in: kde-guidance (Ubuntu)
> Assignee: (unassigned) => Luka Renko (lure)
> Status: New => Incomplete
>
> --
> [gutsy] power manager powersave mode works incorrectly
> https://bugs.launchpad.net/bugs/133357
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
-Joshua

Thanks for responding back quickly. Since we cannot debug this anymore (HW not available), I will close it as Invalid. Feel free to re-open if you experience similar problem again (on any HW).