Hi!

I'm having trouble with powersave on my laptop. When I start KDE, I'm being told by KPowersave that powersaved is not running. So I took a look and found out that it is running (both acpid and powersaved are on the process list). I tried then to use the console to tweak the settings with powersave. The problem was that that was OK when I was root, but when I tried to do the same stuff as a user, powersave failed with error like: "An error occured. Make sure that the powersave daemon is running and use -v to increase verbose level and have a look into syslog."

So I looked at the syslog. I found the following: "[powersave]: ERROR (dbusSendMessageGeneric:209) Error: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "com.novell.powersave.request" member "SchemesGet" error name "(unset)" destination "com.novell.powersave")".

What does this all mean? Should I change permissions or something?

Thanks

I have just recently recompiled my kernel and remember seeing an option to allow users to engage power saver mode while doing my config. I don't remember where it was exactly so you will need to look around for it. Enabling it in the kernel should fix the problem.

let me know how it goes,
...drkstr

Hmmm.... OK, thanks a lot for the advice. Have only stock 2.6.16 kernel. I'll try to compile a kernel from source as soon as I come home this afternoon.

But as far as the error messages go, it's the dbus configuration that is not allowing inter-process communication? Is this somehow bound by kernel too then? Because I tried to edit dbus config file. I even tried to allow all communication (which of course can be potentially dangerous). But with no luck The same message in syslog and the same error on KDE startup...

Now the funny thing is that I am able to query info about battery, fans and such (eg. powersave -F or -T or -B) without any problems. Though when I'm trying to list schemes with powersave -x I get the usual "An error occured. Make sure that the powersave daemon is
running and use -v to increase verbose level and have a look into syslog."

Increasing verbosity doesn't help either...

So I just hope that your suggestion works. Anyway thank you very much for the help

Ehmm.... Sorry if this sounds stupid, but cannot find that option in the kernel configuration. Do you remember where you saw it? Cause I've been through the menuconfig a couple of times now and I can't find any trace of it. But then again it's rather late already and it's been long since my last coffee

I am running 2.4 kernel so I'm not sure if it's in the exact same place, but I found it here:

General Setup->Power Management Support->Advanced Power Management BIOS support

There are a few kernel option in this last category that might be useful to your problem. Ignore User suspend being one of them. I am not an expert on BIOS stuff so you might want to read up a little bit about your BIOS and figure out which options are right for your hardware.

I don't know for sure that this is what's causing your problem, but it seemed like it might be important to configure you kernel to correctly use your BIOS.

regards,
...drkstr

Thanks a lot for taking time to look at the kernel config again

Yeah, I saw that option but I thought it wasn't the right one since it was disabled by default (I guess the same configuration is used for the pre-kernel in Debian too?) So now I'm compiling the newly-configured kernel. Will come back and tell how it goes

Well, I have now recompiled my kernel several times with no success. Upgraded powersave. No results. The same dbus problem. Some other advice, anyone?

On the positive side I've got hibernating to work after recompiling the kernel, so that's at least something. Though suspend and standby still don't work.

Hopefully this could be of some use to you.

http://www.gentoo.org/doc/en/power-management-guide.xml

regards,
...drkstr