Gdm PAM issue/query

General Discussion
1

When I use lightdm for my login manager I get PAM control, in that when I first try going onto something like google chrome it asks me for authentication to unlock my keyring. However when I login via gdm it does not. I noticed when asking for the status of each of these login managers that gdm is reporting some sort of error about PAM. That is…

systemctl status gdm

● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; disabled; vendor preset: disabled)
Active: active (running) since Wed 2020-07-08 23:34:40 EDT; 32min ago
TriggeredBy: ● gdm.path
Process: 1023 ExecStartPre=/usr/libexec/gdm-wait-for-drm (code=exited, status=0/SUCCESS)
Main PID: 1025 (gdm)
Tasks: 4 (limit: 77002)
Memory: 14.3M
CGroup: /system.slice/gdm.service
└─1025 /usr/bin/gdm

Jul 08 23:55:40 CLR-JoshuAmy gdm-Xorg-:2[7436]: for help.
Jul 08 23:55:40 CLR-JoshuAmy gdm-Xorg-:2[7436]: (EE) Please also check the log file at “/dev/null” for addit>
Jul 08 23:55:40 CLR-JoshuAmy gdm-Xorg-:2[7436]: (EE)
Jul 08 23:55:40 CLR-JoshuAmy gdm-Xorg-:2[7436]: (EE) Server terminated with error (1). Closing log file.
Jul 08 23:55:40 CLR-JoshuAmy gdm[1025]: GdmDisplay: Session never registered, failing
Jul 08 23:55:47 CLR-JoshuAmy gdm-password][7491]: gkr-pam: unable to locate daemon control file
Jul 08 23:55:47 CLR-JoshuAmy gdm-password][7491]: gkr-pam: stashed password to try later in open session
Jul 08 23:55:47 CLR-JoshuAmy gdm-password][7491]: pam_unix(gdm-password:session): session opened for user Jo>
Jul 08 23:55:47 CLR-JoshuAmy gdm-password][7491]: gkr-pam: gnome-keyring-daemon started properly and unlocke>
Jul 08 23:55:49 CLR-JoshuAmy gdm[1025]: Child process -6727 was already dead.

while in lightdm I don’t get this message about PAM see below…

lightdm.service - Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2020-07-08 23:34:35 EDT; 34min ago
Main PID: 800 (lightdm)
Tasks: 87 (limit: 77002)
Memory: 220.7M
CGroup: /system.slice/lightdm.service
├─ 800 /usr/bin/lightdm
├─ 836 /usr/bin/X :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
└─7383 /usr/bin/X :0 -seat seat1 -auth /var/run/lightdm/root/:0 -nolisten tcp

Jul 08 23:34:35 CLR-JoshuAmy systemd[1]: Starting Display Manager…
Jul 08 23:34:35 CLR-JoshuAmy systemd[1]: Started Display Manager.
Jul 08 23:34:36 CLR-JoshuAmy lightdm[954]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jul 08 23:34:40 CLR-JoshuAmy lightdm[957]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jul 08 23:35:01 CLR-JoshuAmy lightdm[1285]: pam_unix(lightdm:session): session opened for user Joshua by (uid=0)
Jul 08 23:46:25 CLR-JoshuAmy lightdm[4832]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jul 08 23:46:47 CLR-JoshuAmy lightdm[4882]: pam_unix(lightdm:session): session opened for user Joshua by (uid=0)
Jul 08 23:55:40 CLR-JoshuAmy lightdm[7433]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jul 09 00:04:31 CLR-JoshuAmy lightdm[9515]: pam_unix(lightdm:session): session opened for user admin by (uid=0)

Is this an error or by design? Should this be sent to the developers, or is this a find place to post? I’m fairly new to Clear Linux having been using debian for about 10 year before.

2

I don’t know why you are trying to use lightdm instead of gdm when using Gnome… Well, I’d suggest you install xfce/lightdm settings (possibly from source) to enable Gnome Keyring after login

3

I would prefer to use gdm.

But the root cause is that I am intending to run my Clear Linux box in multiseat. Lightdm works out of the box with no additional setup from me. gdm does not.

When I tried to create a file /etc/gdm/gdm.conf for additional setup for multiseat it does not seem to read the file from there. I have not found where the file is suppose to be kept. If you know, please enlighten me.

But either way, when debugging I noticed that systemctl status gdm was reporting errors, I figured this might be of some interest to the developers of Clear Linux. Hence why I posted it here and comparing it to the output from lightdm.

4

Check this line

5

Thanks That at least let’s me know where and what name to give the file. Now I just have to get a working custom.conf file together.