Bug#653011: Status?

Yves-Alexis Perez corsac at debian.org
Tue Mar 13 15:19:58 UTC 2012


So it's not completely clear what's the status on this bug.

As far as I can tell, it happens when not all keyring components are
started (for example because user is not under GNOME, with dbus-based
activation, or OnlyShowIn).

In my case, I don't use pkcs11 or ssh components (and don't want to). I
do use the “secret” components (and it's correctly started, here under
Xfce) for Evolution, but that's all.

When I run an svn up, something still think it'd be a good idea to ask
gnome-keyring, and find some way to do it, since GNOME_KEYRING_CONTROL
is defined. Though there's no chance it'll be able to contact the pkcs11
component, so it failed with the same error:

WARNING: gnome-keyring:: couldn't connect
to: /tmp/keyring-Ladxda/pkcs11: No such file or directory

Commenting:

module: gnome-keyring-pkcs11.so

in /etc/pkcs11/modules/gnome-keyring-module at least workarounds the
problem (the message disappears) but I'm not sure if it's the correct
way to do it. And if it is, I wonder if it should be made so that it's
consistent with what's currently running.

Regards,
-- 
Yves-Alexis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20120313/2a453449/attachment.pgp>


More information about the pkg-gnome-maintainers mailing list