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

[Kevin Krammer]

On Friday 01 June 2007, Stephen Dowdy wrote:

> Thanks, that sounds about right.  I am trying to figure out how to use the
> advice given by Thiago Macieira in
> http://lists.kde.org/?l=kde-devel&m=117999953011496&w=2
>
> "...You can tell klauncher to re-add it via DCOP (setLaunchEnv), once it's
> up and running...."
>
> This appears preferable to modifying the system installation, as this can
> be documented for my normal users to use instead of having to mangle
> things as 'root'.
>
> I tried:
>
> # dcop klauncher klauncher setLaunchEnv LOCALDOMAIN "$LOCALDOMAIN"
> (i tried other variable settings, too)
>
> but that doesn't seem to have any effect on the mini-cli's
> running environment.  (there's no error messages)

I think your conclusion about the different environment is correct.
This alters the environment klauncher use for starting applications, but does 
not change the environment of already running applications.

I think Thiago's suggestion was meant to be applied in startkde, right after 
the "wrong-doer" removed the settings from the enironment.

> I suspect the mini-cli shell would somehow need to be restarted to acquire
> the environment from 'klauncher'?  Is that possible?

mini-cli is provided by kdesktop, you could try restarting it.
Maybe also kicker, since it provides the K menu.

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde/attachments/20070602/c8cdda58/attachment.sig>
-------------- next part --------------
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.