[PLUG] Run a simple script at KDE startup

[Paul Mullen]

On Tue, Dec 12, 2006 at 05:01:09PM -0800, Denis Heidtmann wrote:
> I edited kcmdisplayrc using Kate, (invoked with kdesu).  Then I
> logged out and logged back in. Is this a problem?

My suspicion (untested) is that KDE would re-write kcmdisplayrc upon
logout, leaving the file's contents the way it thinks they should be.
Have you checked kcmdisplayrc again since you logged out and back in,
just to verify that it's still the way you set it? If you really
wanted to hand-edit kcmdisplayrc, you would probably have to do it
while there is no KDE session running, in order to avoid having KDE
step all over your changes.

> The values reported by xset do not match the values in kcmdisplayrc.
> To do so, they should be 60,120,180 seconds.  Where do 20, 30, and
> 40 minutes come from?

Probably the values that are set via KDE.

> Using Systemsettings (the replacement for kcontrol) gives me only
> one time option, and as a result, sends the command xset dpms 60 60
> 60 (for a 1 minute time).

System Settings is an Ubuntu thing, IIRC? I'm not sure why it doesn't
offer the full complement of display power management settings. Can
you still right-click on the desktop and get to the "Configure
Desktop..." control panel? On my system, the "Display" section of that
control panel has a "Power Control" tab with options for standby,
suspend, and power-off.

> If I execute sudo kcontrol from a termminal window, I get errors,
> and no access to monitor power:

You should be able to run kcontrol as a regular (non-root) user. If a
particular panel requires root privileges, it'll ask for the password.

> Pythonize constructor -- pid = 4788
> Xlib: connection to ":0.0" refused by server
> Xlib: No protocol specified

It's dying because root cannot (without some trickery) run GUI-based
apps on a display belonging to a regular user's login. Just hit F2 and
run 'kcontrol' like any other app.

-- 
Paul