That should not occur, and it could possibly be that the user configuration files were not writable by the user, or that the administrator had overridden the setting using the Kiosk framework ( immutable configuration entries )

It could also be possible that KDE Daemon (kded) was running as another user, yet still attached to your session.

If all of the above is not correct, then please file a bug at bugs.kde.org.

I spoke too soon it only worked until I rebooted and the problems back. Kcm should have never been removed as it took care of these problems. Just turn it on and tell it to never do anything with 3 simple controls. Well I guess Im going back to a distro using an earlier release until these bugs are gone. Peace guys.

I think I've found a satisfactory workaround for my desktop.

I start PowerDevil, let it manage the screen and tell it to keep power on for 360 mins. Now the screensaver kicks in and it is a rare event that I have the screen conk out on me...

Did any of those who experience this problem use the old KCM ( which conflicted with PowerDevil functionality and was removed in 4.4 )?

This is an issue I've had from the very beginning of
the install of openSuSE 11.2. Very annoying. I have
gone through and disabled or unchecked every power
managing function I can find and yet the screen still
blacks out after a few minutes sitting idle.

Command: qdbus org.kde.kded /kded loadedModules | grep power
Output: Service 'org.kde.kded' does not exist.

No idea about PowerDevil install since I am unable to
find anything as far as a control panel for it. I did
uncheck the power management option for it to control
the power scheme but that's as far as I've gotten with
anything to do with PowerDevil.

Aside from this glitch/issue, KDE is still my most
favorite of the GUI's... keep it up!

Thanks.

Computer: HP Mini 1035nr
Linux: 2.6.31.12-0.2-desktop i686
System: openSUSE 11.2 (i586)
KDE: 4.3.5 "release 0"
RAM/SWAP: 2GB/2GB

@RegLinUsr: Your system appears to have a major issue if KDE Daemon is not accessible via D-Bus. Did you run that command from a terminal ( such as Konsole) launched from inside your session?

Well, it seems that I get different outputs depending upon which
terminal client and/or mode I'm in.

Using "Terminal - Super User Mode" terminal:
Command: qdbus org.kde.kded /kded loadedModules | grep power
Output: Service 'org.kde.kded' does not exist.

Using "Terminal" [as non-root user]:
Command: qdbus org.kde.kded /kded loadedModules | grep power
Output: powerdevil

Using "Terminal" [invoking su]:
Command: qdbus org.kde.kded /kded loadedModules | grep power
Output: Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply:
Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.

Trouble-shooting is so much fun!

Unless otherwise stated, commands should always be run as your own user ( so the non-root output is what I expected, and your system is normal )

bcooksley wrote:... output is what I expected, and your system is normal )

"Normal" being what exactly? How do I access PowerDevil settings/configuration
and/or disable it to verify that it may be the culprit for this issue?

PowerDevil can be disabled in System Settings > Advanced > Service Manager. Note that you need to logout and back in again for the setting to take full effect.

Well, I've just about given up on this issue... nothings seems to be working so it must be a bug. Doesn't seem to have been a recent one neither. I've found searches that listed earlier problems with same issue.

This post has been around. I have the same issues with powerdevil. It seems that DPMS settings over ride powerdevil? I can change the monitor settings in the kde setting panel, which show the changes in dpms by reviewing the output of xset -q. These changes will affect the monitor behavior. No matter what I put in powerdevil, dpms settings are the ones that are used. If I disable dpms then the screensaver doesn't work.

I guess that these to systems don't play well together.(?) I have googled it quite a bit in the past and find lots of issues but no solutions. I have fiddled with this problem on and off for some time; both on Fedora in the past and currently Opensuse 11.2.

Maybe if powerdevil modified the dpms settings that one daemon could do it all. Maybe I am missing something?

I just let DPMS handle the monitor and let powerdevil handle the suspend/shutdown of the computer. All this is regarding my laptop. But I have seen it on regular pc as well. Its a pain and haven't figured it out.

I recall that on one box it was necessary to change the power saving options in the BIOS before it would work as I wanted it to.

Decided to play with it again this morning and I figured this much out:

When the computer boots, and I check xset -q, it shows the dpms settings from the KDE power manager. If I change the screen settings in powerdevil, click apply and check xset -q again, they don't change. Still set to whatever KDE has set.

Now, if I unplug the laptop so it is running on battery, powerdevil sees that and changes power schemes. If I then check xset -q, the dpms settings now reflect the powerdevil settings. If I plug the laptop back in, powerdevil again sees the event and changes schemes back to performance. Now xset -q shows powerdevil's performance settings. In either case ( leave it plugged in or not ) the laptop works like you would expect it to using the powerdevil settings. Powerdevil is changing dpms.

Apparently, powerdevil has to see an event before it updates the settings. Clicking apply in pwerdevils cfg screen does not trigger the change - why? Is this a bug in the program?

If I just boot the laptop and leave it plugged in it will follow the KDE settings which is not what people expect. Sooooo, I am thinking that, on boot, KDE sets dpms last maybe and thats why those settings stick? Is there a way to stop KDE from handling power management? If I turn it off in kde I am sure thats what I'll get on reboot.

Lot of effort over just turning the monitor off - lol. It would be cool to resolve though.

Note that in KDE 4.4 the DPMS settings panel has been removed, so it shouldn't be an issue in KDE 4.4 or later as only Powerdevil should be setting the DPMS settings.