Bug 299733

Summary: Power management clients have to use new PolicyKit API
Product: [openSUSE] openSUSE 10.3 Reporter: Andreas Schneider <anschneider>
Component: Mobile DevicesAssignee: Danny Al-Gaaf <dalgaaf>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None CC: aj, funtasyspace, rainer.lay
Version: Beta 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Andreas Schneider 2007-08-13 09:46:14 UTC
kpowersave doesn't work with the new PolicyKit from your Build Service home.

kpowersave: ERROR: Could not send dbus message: The name org.freedesktop.PolicyKit was not provided by any .service files.
Comment 1 Holger Macht 2007-08-13 10:03:12 UTC
Same issue exists for the powersave command line client.
Comment 2 Danny Al-Gaaf 2007-08-13 10:46:29 UTC
I don't see any problem with this message, it's only the info that there is no PolicyKit daemon running. Besides this everything work correct. We may port later to newer PolicyKit.
Comment 3 Holger Macht 2007-08-13 11:17:09 UTC
But this is definitely no 'minor' problem. It breaks suspend to anything from the desktop and even partly from the command line. liblazy has to be adjusted, too.
Comment 4 Danny Al-Gaaf 2007-08-13 12:27:11 UTC
No, it doesn't break suspend from KPowersave. If KPowersave can't access PolicyKit via D-Bus it try to suspend anyway. What break suspend is bug #298943. There is no problem with KPowersave. 

@Holger: I reassign the bug to you if you have problems with liblazy etc.
Comment 5 Andreas Jaeger 2007-08-14 14:36:44 UTC
powersave -u and powersave -U both failed for me with the new hal/ConsoleKit/PolicyKit due to PolicyKit 
Comment 6 Holger Macht 2007-08-16 09:42:19 UTC
*** Bug 300602 has been marked as a duplicate of this bug. ***
Comment 7 Holger Macht 2007-08-16 10:14:31 UTC
kdebase3 is affected, too.
Comment 8 Holger Macht 2007-08-17 17:38:16 UTC
Fixed packages liblazy, powersave, wmpowersave and kdebase3 submitted to STABLE.
Comment 9 Jörg Hermsdorf 2007-08-20 14:44:24 UTC
I just updated to the latest FACTORY packages, but Suspend-to-RAM and Suspend-to-disk don't work here on my system. The only thing that happens, when I try to S2RAM or S2DISK via kpowersave is that the screen gets locked.

liblazy 0.2-5
powersave 0.15.16-3
kpowersave 0.7.2_SVN20070724-15
kdebase3 3.5.7-53
PolicyKit 0.4-11
ConsoleKit 0.2.1-41.2
hal 0.5.9_git20070816-2
Comment 10 Holger Macht 2007-08-20 14:50:21 UTC
Ok, reassigning to Danny. That sounds like what I've also discovered. There's definitely something wrong...
Comment 11 Holger Macht 2007-08-20 14:51:02 UTC
KPowersave...
Comment 12 Danny Al-Gaaf 2007-08-20 15:27:28 UTC
Sorry, but this has nothing to do with this bug. This bug was about implement a new API and not a bug about call suspend. May you should take a look at bug #298943
Comment 13 Andreas Schneider 2007-08-22 09:32:35 UTC
Suspend works for me with latest kdebase3, kdebase3-kdm and kdelibs3 packages.