Summary: | kde-base/powerdevil-4.3.3[+pm-utils] does not support suspend and hibernate anymore | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Kahle (RETIRED) <tomka> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | mlengyel |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Thomas Kahle (RETIRED)
2009-12-11 11:29:35 UTC
What pm-utils and hal versions? (In reply to comment #1) > What pm-utils and hal versions? > I am using the x86 stable versions: pm-utils-1.2.5 with use flags: alsa video_cards_intel hal-0.5.13-r2 with use flags: X acpi consolekit crypt kernel_linux laptop policykit Another observation: Powerdevil shows under "Capabilities" a warning that consolekit was not found active or Powerdevil cannot connect to it... /etc/init.d/consolekit status shows "stopped" but it cannot be started because /etc/init.d/consolekit start * Starting ConsoleKit daemon... * start-stop-daemon: /usr/sbin/console-kit-daemon is already running (In reply to comment #2) > (In reply to comment #1) > > What pm-utils and hal versions? > > I am using the x86 stable versions: > pm-utils-1.2.5 with use flags: alsa video_cards_intel > hal-0.5.13-r2 with use flags: X acpi consolekit crypt kernel_linux laptop > policykit > > Another observation: > Powerdevil shows under "Capabilities" a warning that consolekit was not found > active or Powerdevil cannot connect to it... hmm, did you enable the consolekit use flag in /etc/make.conf or for each package in /etc/portage/package.use{/*} ? Make sure you built kdm and hal with consolekit. Also check if you enabled policykit for consolekit and hal and that you have policykit-kde installed.
> hmm, did you enable the consolekit use flag in /etc/make.conf or for each
> package in /etc/portage/package.use{/*} ? Make sure you built kdm and hal with
> consolekit. Also check if you enabled policykit for consolekit and hal and that
> you have policykit-kde installed.
-) I rebooted with consolekit now in the default runlevel. This does not change anything.
-) I have the consolekit use flag enabled in /etc/make.conf.
-) I do not use kdm, but startx with /usr/bin/startkde script.
-) hal and consolekit have the policykit useflag set, policykit-kde is installed.
-) As it worked fine before, did consolekit/policykit change from kde-4.3.1 to 4.3.3 ?
-) kde-4.3.3 went stable the same day like some new X packages (xorg-server-1.6.5-r1 and deps).
Could any of these cause this?
Bug #281042 seems to discuss the consolekit issue. I am not sure whether it is the source of the suspend problem. Ok, after some tideous investigation I solved this one. It is a policy issue. My user is not allowed to suspend the computer. This can be changed by root if he starts up the kde system settings and then under "Advanced->PolicyKit Authorization" identifies the correct entries under org.freedesktop and sets them to an appropriate value. For instance org.freedesktop.hal.power-management.suspend should have the implicit authorization "anyone -> Yes" to make powerdevil work again. I have no idea what triggered this change in my systems configuration. Now, it seems like a configuration issue, where the package maintainer of these rules should decide upon standard values, like whether users are allows to suspend the system. Is it still a bug? If yes, against which package? (In reply to comment #5) > Bug #281042 seems to discuss the consolekit issue. I am not sure whether it is > the source of the suspend problem. And i forgot to mention. It seems unrelated to the above problem which still persists. It is a consolkit problem. I had the same problem with consolekit-0.4.1. Changed back to consolekit-0.3.0-r2 and kde and powedevil works for suspend. Maybe the ebuild for powerdevil should be changed to request consolekit-0.3.0-r2. BTW: Problem persists with powerdevil-4.3.4 I do have powerdevil-4.3.4 installed, and with consolekit-0.3.0-r2 suspend works for me. Please note that by comment 6, I can also suspend after changing some policies. Sorry. I should read the comments better. :-) Putting back consolekit-0.4.1 and (Make sure that the configuration file is updated.) and doing comment #6 (except that I gave explicit permition to my user, powerdevil-4.3.4 works fine for me. Something happend. It might be hal related. It stopped working after updates with consolekit-0.4.1. I had to go back to consolekit-0.3.0-r2. It works now. -) I can't reproduce any failure here -) Initial problem was a configuration problem during migration If you're having trouble with consolekit please open a new bug or comment on the existing ones. Closing. Thanks. |