spurious warning about gnome-keyring-pkcs11.so

Bug #888199 reported by Serge Hallyn
40
This bug affects 9 people
Affects Status Importance Assigned to Milestone
p11-kit (Ubuntu)
Undecided
Unassigned

Bug Description

Install seahorse and libvirt on a host. Log in remotely, and do 'virsh list'. You'll see:

serge@p-libvirt:~$ virsh list
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
 Id Name State
----------------------------------

That first line shouldn't be there. When logged in with a gnome session, the warning is not there. Since it doesn't affect functionality it should not be displayed (though at least it is on stderr, not stdout).

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

A workaround is to create the file:

$HOME/.pkcs11/modules/gnome-keyring

containing a single line:

module:

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Actually I guess that per

http://ubuntuforums.org/showthread.php?p=11381161#post11381161

this might be a multiarch issue. Though working around that still gives me an error about "no socket to connect to".

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Actually the workaround in comment #1 isn't working for me any more. I had to actually rm /etc/pkcs11/modules/gnome-* . After that the warning disappeared.

Revision history for this message
dino99 (9d9) wrote :

Related multiarch report: Bug #859600

Revision history for this message
Steve Langasek (vorlon) wrote :

Is this an issue in current precise, or was this only present in 11.10 - or a transient issue earlier in precise?

Revision history for this message
Serge Hallyn (serge-hallyn) wrote : Re: [Bug 888199] Re: spurious warning about gnome-keyring-pkcs11.so

> Is this an issue in current precise, or was this only present in 11.10 -
> or a transient issue earlier in precise?

It's an issue in current precise. I just reproduced it by taking a new
precise server install which had libvirt-bin, doing

    sudo apt-get -y install gnome-keyring

after which

 virsh list

showed

 WARNING: gnome-keyring:: no socket to connect to

This was not ever an issue in oneiric (at least up until after precise
development began - I have no oneiric around at the moment)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in p11-kit (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

Got this error while updated Precise i386 +gnome-classic:

Dépaquetage de la mise à jour de hplip-gui ...
Traitement des actions différées (« triggers ») pour « man-db »...
Traitement des actions différées (« triggers ») pour « cups »...
WARNING: gnome-keyring:: no socket to connect to
WARNING: gnome-keyring:: no socket to connect to
Updating PPD files for hpcups ...
PPD for printer Photosmart-C4500-series updated
PPD for printer Photosmart_C4500 updated
Updating PPD files for hpijs ...

Seems that issue is very close to bug : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649408, mainly post #70 +

Revision history for this message
dino99 (9d9) wrote :

by the way, this package is not installed by default, as i can see, and there is no dependant package when checking into synaptic.
There is no p11* package installed on my system, only libp11-kit0 0.9-3

Revision history for this message
Sami Kerola (kerolasa) wrote :

sudo apt-get install gnome-keyring

worked for me

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.