Problem with startkde ~/.kde/env/*.sh and environment sanitizing

Stephen Dowdy sdowdy at
Thu May 31 22:48:47 BST 2007

I have a script that exists as ~/.kde/env/

This script contains:

export LOCALDOMAIN=" blah.blah boo.hoo"

I can see from adding diagnostic statements into /usr/bin/startkde that this
script is indeed sourced and that, after sourcing, the environment contains

I see that this variable is no longer in the environment when attempting
to reference it from the mini-cli.  Other variables i setup in or
other ~/.kde/env/*.sh scripts *DO* exist.

I suspect that since this worked in Debian Sarge (kde 3.3.2), but no longer
does in Debian Etch (KDE 3.5.5) that someone got the bright idea to sanitize
the environment for potential security issues.  (clearly LOCALDOMAIN *could*
be used to compromise an end-user's environment).

However, i don't want to be "protected from myself", but i can NOT figure out
where this sanitizing process occurs and more importantly, how to DISABLE it.
(or effectively work around it)

Any clues greatly appreciated!

Stephen Dowdy  -  Systems Administrator  -  NCAR/RAL
303.497.2869   -  sdowdy at        -

This message is from the kde mailing list.
Account management:
More info:

More information about the kde mailing list