Public bug reported:

After upgrading to Ubuntu 17.10 and switching to GDM3 for my display
manager, gnome-keyring-daemon doesn't seem to be correctly creating its
auth agent socket.

I get an environment variable correctly set:

⟫ export | grep SSH
declare -x SSH_AUTH_SOCK="/tmp/chromoting.tessa.ssh_auth_sock"

but when I look at that file, it doesn't exist:

⟫ ls -lh ${SSH_AUTH_SOCK}
ls: cannot access '/tmp/chromoting.tessa.ssh_auth_sock': No such file or 
directory

and so things like ssh-add don't work.

gnome-keyring-daemon is running however, so it hasn't failed completely.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-keyring 3.20.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct 23 11:02:22 2017
InstallationDate: Installed on 2016-07-08 (471 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to artful on 2017-10-19 (3 days ago)

** Affects: gnome-keyring (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug artful third-party-packages wayland-session

-- 
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/1726522

Title:
  gnome-keyring-daemon doesn't create auth socket

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 17.10 and switching to GDM3 for my display
  manager, gnome-keyring-daemon doesn't seem to be correctly creating
  its auth agent socket.

  I get an environment variable correctly set:

  ⟫ export | grep SSH
  declare -x SSH_AUTH_SOCK="/tmp/chromoting.tessa.ssh_auth_sock"

  but when I look at that file, it doesn't exist:

  ⟫ ls -lh ${SSH_AUTH_SOCK}
  ls: cannot access '/tmp/chromoting.tessa.ssh_auth_sock': No such file or 
directory

  and so things like ssh-add don't work.

  gnome-keyring-daemon is running however, so it hasn't failed
  completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 23 11:02:22 2017
  InstallationDate: Installed on 2016-07-08 (471 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to artful on 2017-10-19 (3 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to