Ubuntu
gnome-keyring package

GNOME keyring often fails to unlock in XFCE

Bug #1022322 reported by Joshua O'Leary on 2012-07-08

This bug report is a duplicate of: Bug #932177: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11. Edit Remove

112

This bug affects 25 people

Affects		Status	Importance	Assigned to	Milestone
	gnome-keyring (Ubuntu)	Confirmed	Undecided	Unassigned

(?)

Bug Description

GNOME Keyring often fails to unlock at login in XFCE, other users in the xubuntu-users mailing list have also reported this. It affects applications using the gnome-keyring framework, including chromium / google chrome.

The file causing the problem is /etc/xdg/autostart/gnome-keyring-pkcs11.desktop . The line
OnlyShowIn=GNOME;Unity
should be changed to
OnlyShowIn=GNOME;Unity;XFCE

to enable gnome-based applications using the keyring to run properly under XFCE.

dpkg -S gnome-keyring-pkcs11.desktop
gives
gnome-keyring: /etc/xdg/autostart/gnome-keyring-pkcs11.desktop
so the package that needs to be fixed is definitely gnome-keyring.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-keyring 3.2.2-2ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic i686
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
Date: Sun Jul 8 17:29:21 2012
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop: [modified]
mtime.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop: 2012-07-08T17:29:16.745464

Tags: Edit Tag help

Joshua O'Leary (jmoleary) wrote on 2012-07-08:

Dependencies.txt Edit (3.7 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (297 bytes, text/plain; charset="utf-8")

Joshua O'Leary (jmoleary) wrote on 2012-07-08:

Note: the only reason gnome-keyring-pkcs11.desktop has been marked as 'modified' is because I had to experiment with the file in order to find the solution with this bug, but the file in the original state has been reported as causing the problem.

Launchpad Janitor (janitor) wrote on 2012-07-09:

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

Changed in gnome-keyring (Ubuntu):
status:	New → Confirmed

ged byrom (ged-byrom269-h) wrote on 2012-07-12:

This bug affects me on several machines with fresh installs of xubuntu 12.04 and one that was upgraded from xubuntu 11.04.
Embarrassingly some of the machines were for other people.

Kevin Brubeck Unhammer (unhammer) wrote on 2012-12-13:

Note: when upgrading to 12.10, it tries to remove XFCE from the list and add MATE (though asks you whether to accept the change). So I'm guessing this bug is still open.

Amir Eldor (amireldor) wrote on 2013-01-15:

I believe it's not only in XFCE. I'm using Mint 13 with MATE and it started showing this error when I try to push on git. SSH is working just fine though.

BitBurners.com (lasse-penttinen) wrote on 2013-02-03:

This has started to appear on my Xubu 12.10 64bit after couple of months of problem free usage.

Jason Smith (marinecomm) wrote on 2013-08-30:

I've been getting this error message lately when running some programs. I'm running Xubuntu 12.04 64-bit. Do I really need gnome-keyring or can I disable/uninstall it?

Jonners59 (jonathan-l-harrison) wrote on 2016-02-20:

I am on 15:10 and i am getting this error too.

Linux version 4.2.0-27-generic (buildd@lgw01-12) (gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ) #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016
# dmidecode 2.12
SMBIOS 2.6 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: P8P67-M PRO
Version: Rev X.0X
Serial Number: MT7014018601056
Asset Tag: To be filled by O.E.M.
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To be filled by O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0