Thanks for the pointer. I did 'dpkg -r dbus-user-session' and rebooted. Now 'pam-afs-session' does the right thing and obtains a token.
However, @poettering points out in the systemd/issues/7261 thread, Are there any downsides? > > Yes, many. You turned off user service management entirely. Hence > "systemctl --user" and all that stuff won't work anymore. On Fri, Aug 17, 2018 at 6:25 AM Andreas Ladanyi <andreas.lada...@kit.edu> wrote: > Hi, > > try to remove the dbus-user-session package and look if it works. > > Have a look at https://github.com/systemd/systemd/issues/7261 > > regards, > > Andy > > Am 17.08.2018 um 02:41 schrieb Prasad K. Dharmasena: > > I've installed OpenAFS and pam-afs-session on Ubuntu 18.04 (bionic) via > (a) vendor supplied packages, and (b) building from source (1.6.22.3). On > both machines, logging in via gdm doesn't get me a token. SSH in, however, > does obtain a token. For both gdm and ssh logins, the auth.log shows the > following: > > pam_afs_session(gdm-password:session): PAG apparently lost, recreating > pam_afs_session(sshd:session): PAG apparently lost, recreating > > Has anyone else seen this on Ubuntu 18.04? (I've had this working for a > while now on Ubuntu 16.04 -- building from 1.6.20+ source with > pam-afs-session 2.6.) > > Thanks. > > > -pkd > > >
