Bug#522266: gnome-keyring is still misbehaving

[Apelete Seketeli]

Package: gnome-keyring
Version: 2.26.0-4
Severity: normal

I'm still having some problems with gnome-keyring too.
Here's a description of the problem:
 - when I log in gnome-keyring sometimes (quite frequently) fails to unlock the keyring (though it is started),
 - mail-notification thus fails to check my mail. If I launch seahorse I'm asked to manually enter the keyring password,
 - after doing so, mail-notification stills fails to connect to the keyring daemon
 - if I end the mail-notification process and relaunch it, problem is solved

I have attached a file containing errors related to the problem (extracted from .xsession-errors).


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.29-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnome-keyring depends on:
ii  dbus-x11     1.2.12-1                    simple interprocess messaging syst
ii  gconf2       2.26.0-1                    GNOME configuration database syste
ii  libc6        2.9-7                       GNU C Library: Shared libraries
ii  libdbus-1-3  1.2.12-1                    simple interprocess messaging syst
ii  libgconf2-4  2.26.0-1                    GNOME configuration database syste
ii  libgcr0      2.26.0-4                    Library for Crypto UI related task
ii  libgcrypt11  1.4.4-2                     LGPL Crypto library - runtime libr
ii  libglib2.0-0 2.20.1-1                    The GLib library of C routines
ii  libgp11-0    2.26.0-4                    Glib wrapper library for PKCS#11 -
ii  libgtk2.0-0  2.16.1-2                    The GTK+ graphical user interface 
ii  libhal1      0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer - share
ii  libpango1.0- 1.24.0-3+b1                 Layout and rendering of internatio
ii  libtasn1-3   1.8-1                       Manage ASN.1 structures (runtime)

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

Versions of packages gnome-keyring suggests:
ii  hal          0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer

-- no debconf information
-------------- next part --------------
** (mail-notification:4343): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4343): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4343): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4343): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4343): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4343): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused
** Message: init gpgme version 1.1.8

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (seahorse:4362): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused
** Message: received SIGTERM signal, exiting

** (mail-notification:4397): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4397): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4397): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4397): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4397): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4397): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4397): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused

** (mail-notification:4397): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-0SX0eL/socket: Connection refused