Bug#528978: /usr/bin/gnome-keyring: evolution is unable to connect to gnome-keyring-daemon

[Petri Kaurinkoski]

Package: gnome-keyring
Version: 2.26.0-4
Severity: important
File: /usr/bin/gnome-keyring

Dear Sirs,

For some reason evolution has had serious problems communicating with
the
gnome-keyring-daemon for a week or so, I did not pay a lot of attention
to
it at first. What happens now when I start evolution, it asks me for the
keyring password, I type it, and it is rejected and reasked. The
.xsession-errors file contains messages like:

e-data-server-ui-Message: Received a password from keyring 'default'.
But looking for the password from 'login' keyring


** (evolution:4147): WARNING **: couldn't read 4 bytes from
gnome-keyring socket: Connection reset by peer

** (evolution:4147): WARNING **: couldn't connect to daemon at
$GNOME_KEYRING_SOCKET: /tmp/keyring-zuFC2o/socket: Connection refused

** (evolution:4147): WARNING **: couldn't communicate with gnome keyring
daemon via dbus: Message did not receive a reply (timeout by message
bus)

(evolution:4147): e-data-server-ui-WARNING **: Unable to find
password(s) in keyring (Keyring reports: The gnome-keyring-daemon
application is not running.)

** (evolution:4147): WARNING **: couldn't connect to daemon at
$GNOME_KEYRING_SOCKET: /tmp/keyring-zuFC2o/socket: Connection refused

** (evolution:4147): WARNING **: couldn't connect to daemon at
$GNOME_KEYRING_SOCKET: /tmp/keyring-zuFC2o/socket: Connection refused

** (evolution:4147): WARNING **: couldn't connect to daemon at
$GNOME_KEYRING_SOCKET: /tmp/keyring-zuFC2o/socket: Connection refused

** (evolution:4147): WARNING **: couldn't connect to daemon at
$GNOME_KEYRING_SOCKET: /tmp/keyring-zuFC2o/socket: Connection refused

(evolution:4147): e-data-server-ui-WARNING **: Unable to create password
in keyring (Keyring reports: Access Denied)


Now I do not know which package upgrade exactly started this behaviour,
but
surely things are not the way they are supposed to be. Using evolution
for
e-mail management became just a major problem and pain.

Best regards,

Petri Kaurinkoski

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

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
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-4                       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.0-2                    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

-- 
 Petri Kaurinkoski <Petri.Kaurinkoski at iki.fi>