desktop-packages team mailing list archive

[Gunnar Thielebein <1271591@xxxxxxxxxxxxxxxxxx>]

I am using gnome-keyring-daemon with ssh-agent capability which broke with the keyring-daemon 3.10.1-1ubuntu4.1.
After downgrading to gnome-keyring=3.10.1 SSH_AUTH_SOCKS is again correctly exposed to the keyring location.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591

Title:
  upstart job race prevents gnome-keyring from being ssh agent

Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in gnome-keyring source package in Trusty:
  Fix Released

Bug description:
  I expect gnome-keyring to be the ssh authentication agent when I am
  logged in to a graphical session.

  Because of what I suspect is a race in upstart jobs, I believe
  SSH_AUTH_SOCK is being overwritten after gnome-keyring starts.

  Perhaps the gnome-session job needs to make sure the ssh-agent job is
  finished?

  [testcase]
  1) Perform desktop login
  2)
  [ "$GNOME_KEYRING_CONTROL/ssh" = "$SSH_AUTH_SOCK" ] && echo Good || Fail

  Expected output: Good

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session 3.9.90-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 22 10:25:59 2014
  InstallationDate: Installed on 2013-11-26 (56 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1271591/+subscriptions