Re: A comment on NetworkManager

["Garry T. Williams" <gtwilliams gmail com>]

[ I call BS on my post :-) ]

On Friday 12 May 2006 09:25, Garry Williams wrote:
> nm-applet will run in KDE just fine.  I added
> 
>   /usr/libexec/gnome-settings-daemon
>   /usr/bin/gnome-keyring-daemon
> 
> to my start-up list.

Unfortunately, this isn't going to get gnome-keyring-daemon hooked
into the KDE session.  The session does not have the keyring
environment variables, so nm-applet cannot contact it.

I didn't notice this because I did not try to use an encrypted network
after setting it up.

Here's how it should actually be done (from
http://bugzilla.ubuntu.com/show_bug.cgi?id=17463 ):

To get KDE to source the environment variables you need for clients to
be able to contact the gnome-keyring-daemon, add this script to your
~/.kde/env directory:

    $ cat ~/.kde/env/start-custom.sh
    #!/bin/sh
    #

    # gnome keyring daemon
    # set env vars, much like ssh-agent
    eval `gnome-keyring-daemon`
    export GNOME_KEYRING_PID GNOME_KEYRING_SOCKET
    set | grep GNOME
    $

To make sure the gnome-keyring-daemon is shut down when you exit the
KDE session, add this script to your ~/.kde/shutdown directory:

    $ cat ~/.kde/shutdown/stop-custom.sh
    #!/bin/sh
    #

    # kill any gnome keyring daemons that we were using
    if [ -n "$GNOME_KEYRING_PID" ]; then
      echo killing gnome-keyring-damon $GNOME_KEYRING_PID
      kill $GNOME_KEYRING_PID
    fi
    $

Make both files executable and readable by your uid.

The startkde script will source executable scripts in the env
directory and will run scripts in the shutdown directory before
exiting the KDE session.

Do not add gnome-keyring-daemon to the KDE Autostart folder.

-- 
Garry T. Williams --- +1 678 656-4579