*** This bug is a duplicate of bug 364514 ***
https://bugs.launchpad.net/bugs/364514
** This bug has been marked a duplicate of bug 364514
cpu frequency is reset to maximum after resume from suspend if governor is
userspace
--
cpu-freq applet has set wrong frequency upon resume from susp
As seb says, this is not a gui issue. This could be considered a dupe
of bug 364514?
--
cpu-freq applet has set wrong frequency upon resume from suspend
https://bugs.launchpad.net/bugs/445186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I'm sorry. It is a System76 Pangolin Performance.
--
cpu-freq applet has set wrong frequency upon resume from suspend
https://bugs.launchpad.net/bugs/445186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
I am having a similar experience since upgrading (both in-place upgrade
and clean install) to Karmic. Additionally (and far more problematic)
when I suspend with the ondemand governor active, the CPU becomes stuck
at the lowest step (800 MHz for my P8700 CPU). All other governors --
conservative,
** Package changed: ubuntu => gnome-power-manager (Ubuntu)
--
cpu-freq applet has set wrong frequency upon resume from suspend
https://bugs.launchpad.net/bugs/445186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Summary changed:
- cpu-freq applet has sets wrong frequency upon resume from suspend
+ cpu-freq applet has set wrong frequency upon resume from suspend
--
cpu-freq applet has set wrong frequency upon resume from suspend
https://bugs.launchpad.net/bugs/445186
You received this bug notification
