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

Bug #887654 reported by Rocksinboxes
60
This bug affects 13 people
Affects Status Importance Assigned to Milestone
gnome-keyring (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

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 when trying to launch thunderbird

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-keyring 3.2.1-0ubuntu1 [modified: usr/bin/gnome-keyring-3 usr/bin/gnome-keyring-daemon usr/lib/gnome-keyring/gnome-keyring-prompt-3]
ProcVersionSignature: Ubuntu 3.1.0-2.3-generic 3.1.0
Uname: Linux 3.1.0-2-generic x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 1.25-0ubuntu1
Architecture: amd64
Date: Tue Nov 8 00:51:04 2011
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111107)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Changed in gnome-keyring (Ubuntu):
status: New → Confirmed
Revision history for this message
herta (herta-vandeneynde) wrote :

Had a similar issue with mailx on an upgraded system. Installing gnome-keyring cleared it for me.
For some reason, a freshly installed server does not have this package either, but does not throw the error. No time to investigate further at present.

# apt-get install gnome-keyring
# dpkg-query -l gnome-keyring Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii gnome-keyring 3.2.2-2ubuntu4 GNOME keyring services (daemon and tools)

Revision history for this message
Bryan McLellan (btm) wrote :

These symptoms occur with multiple packages, including yum. Installing gnome-keyring removed the error for me as well.

Revision history for this message
Petr Praus (petr-praus) wrote :

In my case on Ubuntu 13.04, gnome-keyring was already installed but installing libp11-kit-gnome-keyring helped.

Revision history for this message
Alien (alien4any) wrote :

I had the same problem while running grive.
First I sudo apt-get remove gnome-keyring
Then I apt-get install gir1.2-ubuntuoneui-3.0 gnome-keyring libsyncdaemon-1.0-1 libubuntuoneui-3.0-1 oneconf
  python-ubuntu-sso-client python-ubuntuone-control-panel rhythmbox-ubuntuone seahorse
  software-center ubuntu-desktop ubuntu-sso-client ubuntu-sso-client-gtk
  ubuntu-sso-client-qt ubuntuone-client ubuntuone-client-gnome ubuntuone-client-proxy
  ubuntuone-control-panel ubuntuone-control-panel-qt unity-scope-musicstores
and problem solved.

Revision history for this message
Doug Morse (dm-dougmorse) wrote :

alien4any's solution (post #6) worked perfectly for me after trying several other suggestions found around the net (e.g., getlibs, etc). Ubuntu 12.04 LTS 64-bit. Thanks!

Revision history for this message
Ken Sharp (kennybobs) wrote :

So the problem is that the packages mentioned in these comments are not recommending this package? You need to open bugs for those packages.

As is usual in Ubuntu bugs people have all lumped their problems together, so I'll close this invalid and ask that you open bugs for those individual packages, assuming you first check that those packages do not recommend this package and you installed them correctly.

Workaround is installing this package. gnome-keyring does not have a bug.

Changed in gnome-keyring (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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