Bug 983734

Also experiencing this after clean installation of 42.2 importing user and encrypted home partition from 42.1. No visible error indication. A typical section from "journalctl --unit=display-manager.service" looks like:

Nov 26 18:11:06 host systemd[1]: Starting X Display Manager...
Nov 26 18:11:06 host display-manager[1093]: /etc/vconsole.conf available
Nov 26 18:11:06 host display-manager[1093]: KEYMAP: de
Nov 26 18:11:06 host display-manager[1093]: Command: localectl set-keymap de
Nov 26 18:11:07 host.domain display-manager[1093]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Nov 26 18:11:07 host.domain display-manager[1093]: error: unexpectedly disconnected from boot status daemon
Nov 26 18:11:08 host.domain systemd[1]: display-manager.service: PID file /var/run/displaymanager.pid not readable (yet?) after start: No such file or directory
Nov 26 18:11:08 host.domain display-manager[1093]: Starting service sddm..done
Nov 26 18:11:08 host.domain sddm[1277]: Initializing...
Nov 26 18:11:08 host.domain systemd[1]: Started X Display Manager.
Nov 26 18:11:08 host.domain sddm[1277]: Starting...
Nov 26 18:11:08 host.domain sddm[1277]: Adding new display on vt 7 ...
Nov 26 18:11:08 host.domain sddm[1277]: Display server starting...
Nov 26 18:11:08 host.domain sddm[1277]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{4a47ad16-c608-4cdf-bedf-dc7af5cabedc} -background none -noreset -displayfd
Nov 26 18:11:12 host.domain sddm[1277]: Running display setup script  "/etc/X11/xdm/Xsetup"
Nov 26 18:11:12 host.domain sddm[1277]: Display server started.
Nov 26 18:11:12 host.domain sddm[1277]: Socket server starting...
Nov 26 18:11:12 host.domain sddm[1277]: Socket server started.
Nov 26 18:11:12 host.domain sddm[1277]: Greeter starting...
Nov 26 18:11:12 host.domain sddm[1277]: Adding cookie to "/run/sddm/{4a47ad16-c608-4cdf-bedf-dc7af5cabedc}"
Nov 26 18:11:12 host.domain sddm-helper[1355]: [PAM] Starting...
Nov 26 18:11:12 host.domain sddm-helper[1355]: [PAM] Authenticating...
Nov 26 18:11:12 host.domain sddm-helper[1355]: [PAM] returning.
Nov 26 18:11:13 host.domain sddm-helper[1355]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Nov 26 18:11:13 host.domain sddm[1277]: Greeter session started successfully
Nov 26 18:11:14 host.domain sddm[1277]: Message received from greeter: Connect
Nov 26 18:12:13 host.domain sddm[1277]: Message received from greeter: Login
Nov 26 18:12:13 host.domain sddm[1277]: Reading from "/usr/share/xsessions/plasma5.desktop"
Nov 26 18:12:13 host.domain sddm[1277]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Nov 26 18:12:13 host.domain sddm-helper[1423]: [PAM] Starting...
Nov 26 18:12:13 host.domain sddm-helper[1423]: [PAM] Authenticating...
Nov 26 18:12:13 host.domain sddm-helper[1423]: [PAM] Preparing to converse...
Nov 26 18:12:13 host.domain sddm-helper[1423]: [PAM] Conversation with 1 messages
Nov 26 18:12:13 host.domain sddm-helper[1423]: [PAM] returning.
Nov 26 18:12:13 host.domain sddm[1277]: Authenticated successfully
Nov 26 18:12:13 host.domain sddm-helper[1423]: pam_unix(sddm:session): session opened for user adam by (uid=0)
Nov 26 18:12:15 host.domain sddm[1277]: Auth: sddm-helper exited successfully
Nov 26 18:12:15 host.domain sddm[1277]: Greeter stopped.
Nov 26 18:12:34 host.domain sddm[1277]: Session started
Nov 26 18:12:35 host.domain sddm[1277]: Auth: sddm-helper exited with 1

One thing I forgot to mention: If I login on a virtual terminal so that the encrypted home partition is already mounted when SDDM tries to create a new session, everything works as expected.

Adam,
it may be useful if you put your comments into the github issue tracker:
https://github.com/sddm/sddm/issues/694

This is the official place for sddm development and distro-independent bug reports

I think this is exactly the same as bug#954419 and bug#981013, isn't it?

This should help:
(In reply to Josef Möllers from bug#954419, comment #15)
> As David Kerkhof writes in comment #10, you need to explicitly add pam_mount
> to /etc/pam.d/sddm:
> pam-config --service sddm -a --mount

I'm marking this as duplicate, please feel free to reopen if you think that's wrong.

*** This bug has been marked as a duplicate of bug 954419 ***

Hello Wolfgang,

(In reply to Wolfgang Bauer from comment #4)
> I think this is exactly the same as bug#954419 and bug#981013, isn't it?
> 
> This should help:
> (In reply to Josef Möllers from bug#954419, comment #15)
> > As David Kerkhof writes in comment #10, you need to explicitly add pam_mount
> > to /etc/pam.d/sddm:
> > pam-config --service sddm -a --mount
> 
> I'm marking this as duplicate, please feel free to reopen if you think
> that's wrong.
> 
> *** This bug has been marked as a duplicate of bug 954419 ***

I can confirm that manually adjusting the PAM service works and I will adjust the upstream bug report accordingly. Thanks for the hint!

Best regards, Adam.