https://bugzilla.novell.com/show_bug.cgi?id=222479
rknall@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rknall@gmail.com
------- Comment #41 from rknall@gmail.com 2006-12-27 01:01 MST ------- For all the simple "home users" (especially the KDE ones ) out there, there is a rather simple solution for the situation, starting with the script I posted above. Follow the following steps:
1. Open Konsole by hitting Alt-F2 and enter "konsole" (Enter) 2. Enter "cd bin" in the konsole window 3. Enter "kwrite evolution" in the konsole window - kwrite will start up, now copy the following into the open kwrite window, save it, and close kwrite: ---------------- Copy after this line ------------------ #!/bin/sh
if [ ! $GNOME_KEYRING_PID ] ; then keyring=$(/opt/gnome/bin/gnome-keyring-daemon) if [ $? -eq 0 ] ; then for exp in $keyring; do export $exp; done fi fi
if [ $GNOME_KEYRING_PID ] ; then /opt/gnome/bin/evolution $@ else echo "Gnome Keyring has not been started" ------- Copy until this line, but not the line itself ----------
This script makes use of the fact, that on a Suse 10.2 installation gnome resides under /opt/gnome. This is important.
4. We are back under the console. Now we enter "chmod uog+x evolution" 5. The last command is: "ln -s evolution evolution-2.8"
Now, what have we done? In the path, where Linux searches for executables, the bin subpath of your homedirectory is the very first. Therefore, if there is a script or programm in there, which is named evolution, Linux will start it when you start evolution. As sometimes the KDE entries for evolution start evolution-2.8, we made a shortcut, so that either of the names work. Our script will determine, if the keyring program has been started, and if so, it will start evolution. If the keyring daemon has not been started, it will start the daemon, and store the necessary runtime variables.
The whole problem has nothing to do with evolution being compiled with keyring support, but rather with a sloppy way of starting it. As Suse transitions to Gnome as default desktop, noone anticipated, that KDE users might use programs from Gnome, which will need the keyring manager. I am not sure if there is a subsidiate in the Linux Standard Base for a keyring manager, but for now, if anyone of Novell is listening, please submit a patch, which will start the keyring manager for gnome with kde startup just in case.