Bug#522493: Fwd: Re: doesn't remember passwords

[Rasmus Bøg Hansen]

Package: gnome-keyring

Version: 2.30.0-2
Severity: normal


The exact same thing happens for me using gnome. This occurred after the upgrade to 2.30 in testing.

When logging in from gdm, gnome-keyring-daemon is started:

  8493 ?        Sl     0:00 /usr/bin/gnome-keyring-daemon --daemonize

and environment is set:

moffe at hactar:~$ set|grep -i keyring
GNOME_KEYRING_CONTROL=/tmp/keyring-zf8au0
GNOME_KEYRING_PID=8493
SSH_AUTH_SOCK=/tmp/keyring-zf8au0/ssh

This happens whether gnome keyring service is disabled or enabled from the startup programs in System ->  Preferences.
Ok, so far, but:

moffe at hactar:~$ LANG=C LC_ALL=C seahorse

** (seahorse:9251): WARNING **: DNS-SD initialization failed: Daemon not running
** Message: init gpgme version 1.2.0
** Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
** Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files

** (seahorse:9251): WARNING **: couldn't get default keyring name: Error communicating with gnome-keyring-daemon

and seahorse does not display any keyrings at all (it is perfectly able to read my ssh and gpg keys). nm-applet (which is actually the annoying part) is unable to remember the password for wireless networks.

I just created a fresh user, "test", which on logon starts gnome-keyring-daemon:

  8796 ?        Sl     0:00 /usr/bin/gnome-keyring-daemon --daemonize --login

On this user account everything seems to work fine. Seahorse can connect to the keyring daemon and nm-applet can store the network password.

It seems the --login part is making the difference. But I don't see where the keyring daemon is started and where I can change the parameters? It does not seem to be in $HOME so I do not see why the two accounts start the keyring daemon with different parameters...

Regards
/Rasmus

-- System Information:
Debian Release: squeeze/sid
   APT prefers testing
   APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.33.3 (SMP w/2 CPU cores)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to da_DK.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-keyring depends on:
ii  dbus-x11                      1.2.24-1   simple interprocess messaging syst
ii  gconf2                        2.28.1-3   GNOME configuration database syste
ii  libc6                         2.10.2-6   Embedded GNU C Library: Shared lib
ii  libdbus-1-3                   1.2.24-1   simple interprocess messaging syst
ii  libgcr0                       2.30.0-2   Library for Crypto UI related task
ii  libgcrypt11                   1.4.5-2    LGPL Crypto library - runtime libr
ii  libglib2.0-0                  2.24.0-1   The GLib library of C routines
ii  libgp11-0                     2.30.0-2   Glib wrapper library for PKCS#11 -
ii  libgtk2.0-0                   2.20.0-3   The GTK+ graphical user interface
ii  libtasn1-3                    2.5-1      Manage ASN.1 structures (runtime)

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring          2.30.0-2   PAM module to unlock the GNOME key

gnome-keyring suggests no packages.

-- no debconf information