[Bug 17463] New: optional mechanism to start gnome-keyring-daemon in new kde sessions
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Mon Oct 10 05:36:53 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=17463
Ubuntu | kde
Summary: optional mechanism to start gnome-keyring-daemon in new
kde sessions
Product: Ubuntu
Version: unspecified
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kde
AssignedTo: debzilla at ubuntu.com
ReportedBy: mike+ubuntu at blakeley.com
QAContact: kubuntu-bugs at lists.ubuntu.com
It would be helpful if startkde included an option for gnome-keyring-daemon
startup, similar to existing support for ssh-agent. To take one example, the
network-manager nm-applet relies on gnome-keyring.
Until kde supports this option, it's possible to add a couple of files to the
user-level config: these will be evaluated by startkde during its startup and
shutdown sequences. I haven't been able to test this with nm-applet yet, but
this does allow gnome-keyring-manager to find and open the keyring. Both files
must be readable and executable by startkde:
$ 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
# start-custom.sh
$ 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
# stop-custom.sh
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the kubuntu-bugs
mailing list