[Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco

Sun Oct 20 07:34:54 UTC 2019

*** This bug is a duplicate of bug 1817128 ***
    https://bugs.launchpad.net/bugs/1817128

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

** Changed in: gdm3 (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1818616

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  5 08:22:01 2019
  InstallationDate: Installed on 2016-01-26 (1134 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1818616/+subscriptions