tags 413234 + patch
Fixed this problem in Kubuntu. The patch from there is attached (it's so
small, so it should be able to apply even if the version is different)
The problem is most likely that the hal interface changed; I believe the
number 3 represented the state S3. But in current interface it's a
wake-up time instead, so this should be 0 instead. See:
http://people.freedesktop.org/~david/hal-spec/hal-spec.html#interface-device-systempower
Regards,
Andreas
--
Andreas Wenning <[EMAIL PROTECTED]>
diff -Nur -x '*.orig' -x '*~' kde-guidance-0.8.0svn20080103/powermanager/powermanage.py kde-guidance-0.8.0svn20080103.new/powermanager/powermanage.py
--- kde-guidance-0.8.0svn20080103/powermanager/powermanage.py 2008-03-13 11:31:44.000000000 +0100
+++ kde-guidance-0.8.0svn20080103.new/powermanager/powermanage.py 2008-03-13 11:32:28.000000000 +0100
@@ -547,7 +547,7 @@
""" Run a suspend command, either via HAL or script. """
if SUSPEND_USE_HAL:
try:
- self.computerObject.Suspend(3, dbus_interface="org.freedesktop.Hal.Device.SystemPowerManagement")
+ self.computerObject.Suspend(0, dbus_interface="org.freedesktop.Hal.Device.SystemPowerManagement")
except dbus.DBusException:
pass #we get a DBusException: No reply within specified time
else:
