under KDE, gnome-keyring does not set environment variable

Bug #1407154 reported by Oded Arbel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-keyring (Ubuntu)
New
Undecided
Unassigned

Bug Description

under KDE 5 in vivid, after installing gnome-keyring and libpam-gnome-keyring, the gnome-keyring daemon is running, but its socket directory is not exposed in a $GNOME_KEYRING_CONTROL environment variable, so applications that need the GNOME keyring cannot access it.

To workaround I've added the following to the .bash_profile , but its not really a long term solution:

    [ -z "$GNOME_KEYRING_CONTROL" ] && export GNOME_KEYRING_CONTROL=/run/user/$UID/keyring

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: gnome-keyring 3.14.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Jan 2 22:04:16 2015
InstallationDate: Installed on 2015-01-01 (1 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141230)
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Oded Arbel (oded-geek) wrote :
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.