Your message dated Tue, 8 Mar 2011 11:13:45 +0100
with message-id <[email protected]>
and subject line Closing this bug
has caused the Debian Bug report #523443,
regarding gnome-keyring-daemon not started on demand
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
523443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523443
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-keyring
Version: 2.26.0-3
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

gnome-keyring-daemon is not started when needed. I get:

$ gnome-keyring-manager 

(gnome-keyring-manager:6382): Gtk-WARNING **: GtkSpinButton: setting an
adjustment with non-zero page size is deprecated

** (gnome-keyring-manager:6382): WARNING **: couldn't connect to daemon
at $GNOME_KEYRING_SOCKET: /tmp/keyring-YvV2dt/socket: Verbindungsaufbau
abgelehnt

** (gnome-keyring-manager:6382): WARNING **: couldn't communicate with
gnome keyring daemon via dbus: Failed to execute program
gnome-keyring-daemon: Success


and I also get this in .xsession-error:

** (mail-notification:4092): WARNING **: couldn't connect to daemon at
$GNOME_KEYRING_SOCKET: /tmp/keyring-YvV2dt/socket: Verbindungsaufbau
abgelehnt

** (mail-notification:4092): WARNING **: couldn't communicate with gnome
keyring daemon via dbus: Failed to execute program gnome-keyring-daemon:
Success


Also strange is that gnome-session seems to start gnome-keyring-daemon,
as .xsession-errors contains:
GNOME_KEYRING_SOCKET=/tmp/keyring-YvV2dt/socket
at the very top, but the daemon is not running later on.

It seems this is not #522266.

Any ideas what is going on?

Thanks,
Joachim

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

Kernel: Linux 2.6.28-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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.24.0-7                    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.24.0-7                    GNOME configuration database syste
ii  libgcr0      2.26.0-3                    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-3                    Glib wrapper library for PKCS#11 -
ii  libgtk2.0-0  2.14.7-5                    The GTK+ graphical user interface 
ii  libhal1      0.5.12~git20090406.46dc48-1 Hardware Abstraction Layer - share
ii  libpango1.0- 1.24.0-3                    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-3   PAM module to unlock the GNOME key

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

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknfG90ACgkQ9ijrk0dDIGw4NACfaeAKgzqOp2ze356DlfjYfaVp
m7cAnjUSYo3dEfnp21m622vveTv3WDpM
=ETpG
-----END PGP SIGNATURE-----



--- End Message ---
--- Begin Message ---
Version: 2.26.0-4

Closing this bug, as it's fixed in 2.26.0-4 per submitter comment.

Laurent Bigonville


--- End Message ---

Reply via email to