This started happening yesterday in Jaunty beta. The gnome-keyring-daemon no longer runs when I start X, so (for instance) network-manager always asks for the wireless key.
gnome-keyring-daemon is listed as a startup application (Sys/Prefs/Startup Apps) with the command "gnome-keyring-daemon --start". Immediately above it in the list of startup apps is gnome-do, which is disabled.
I can run it manually from the command line and then everything is fine:
rocko@pegasus-jaunty:~$ gnome-keyring-daemon
** Message: couldn't set environment variable in session: Setenv interface is only available during the Initialization phase
GNOME_KEYRING_SOCKET=/tmp/keyring-TXi81Z/socket
SSH_AUTH_SOCK=/tmp/keyring-TXi81Z/socket.ssh
GNOME_KEYRING_PID=5550
I have tried reinstalling gnome-keyring, but it didn't make any difference.
dmesg doesn't show any messages from gnome-keyring.
Binary package hint: gnome-keyring
This started happening yesterday in Jaunty beta. The gnome-keyring- daemon no longer runs when I start X, so (for instance) network-manager always asks for the wireless key.
gnome-keyring- daemon is listed as a startup application (Sys/Prefs/Startup Apps) with the command "gnome- keyring- daemon --start". Immediately above it in the list of startup apps is gnome-do, which is disabled.
I can run it manually from the command line and then everything is fine:
rocko@pegasus- jaunty: ~$ gnome-keyring- daemon SOCKET= /tmp/keyring- TXi81Z/ socket SOCK=/tmp/ keyring- TXi81Z/ socket. ssh PID=5550
** Message: couldn't set environment variable in session: Setenv interface is only available during the Initialization phase
GNOME_KEYRING_
SSH_AUTH_
GNOME_KEYRING_
I have tried reinstalling gnome-keyring, but it didn't make any difference.
dmesg doesn't show any messages from gnome-keyring.
ProblemType: Bug dules: nvidia
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelMo
Package: gnome-keyring 2.26.0-0ubuntu4
ProcEnviron:
LANG=en_AU.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-keyring
Uname: Linux 2.6.28-11-generic x86_64