[Bug 149128] Re: kde-guidance-power-manager changes CPU beahvior to "Performance" after suspend

[Wouter Deconinck]

I can reproduce the problems described above:
- suspend from guidance-power-manager in KDE does not work (for work-around see below), but does work from the lock/logout buttons applet
- resume brings the laptop back up in performance mode when using 2.6.24-4 on x86, but brings it back in ondemand mode (as expected) when using 2.6.24-5 although then guidance-power-manager doesn't show the cpu usage anymore (although the sysfs interfaces are fine)

The first problem (suspend using guidance-power-manager) can be 'solved'
by disabling HAL and DBUS communication in /usr/share/python-support
/kde-guidance-powermanager/powermanage.py by changing:

# Send suspend / hibernate commands to HAL or use Sx_COMMANDS
SUSPEND_USE_HAL = False

# Command to initiate suspend-to-disk when not using HAL
S4_COMMAND = "sudo /usr/sbin/pm-hibernate"
# Command to initiate suspend-to-ram when not using HAL
S3_COMMAND = "sudo /usr/sbin/pm-suspend"

Then run sudo update-python-modules after these changes.  Add the
following lines to /etc/sudoers:

User_Alias      USERS = <usernames>
Cmnd_Alias      SUSPEND = /usr/sbin/pm-hibernate, /usr/sbin/pm-suspend
USERS   ALL = NOPASSWD: SUSPEND


powermanage.py tries to connect to HAL using DBUS at org.freedesktop.Hal.Device.SystemPowerManagement.  This seems to fail (although support for suspend/hibernate using HAL is correctly determined at udi /org/freedesktop/Hal/devices/computer and key .power_management.can_suspend_to_ram).  I tried to investigate with kdbus, but also there the connection seems to fail...  Could this be a DBUS problem?

I have no experience with HAL, DBUS or Python, but I can give more info
if you tell me how to get it.

-- 
kde-guidance-power-manager changes CPU beahvior to "Performance" after suspend
https://bugs.launchpad.net/bugs/149128
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kde-guidance in ubuntu.